This afternoon there was a Cursor update and after that I can’t edit my project files with the agent - I get this error: “EPERM: operation not permitted”. They are stored in a remote server mounted as local using SSHFS (with SSHFS-Win Manager). However I can edit local and Google Drive files.
I can edit the files manually but not with the agent.
Hey, thanks for the report. It looks like this might be related to a known EPERM issue the team is tracking.
A few things that will help us narrow it down:
How is the SSHFS drive mounted, as a drive letter like Z:\ or as a UNC path like \\sshfs\...?
Can you open Developer Tools (Help > Toggle Developer Tools), reproduce the error, and share the full error text from the Console tab?
Do you remember which Cursor version you were on before the update?
Also, a quick workaround to try. Can you check if the issue still happens when you run Cursor as administrator? Since manual edits work but the agent can’t write, it might be that the agent’s write flow, which uses temp files plus rename, is hitting permission limits on SSHFS mounts, while direct writes still go through.
Thank you for your input, I will answer as much as I can.
SSHFS is mounted as X:
In developer tools there are no relevant errors.
Actually what doesn’t work anymore with SSHFS is the method StrReplace, it gives an error ‘EPERM: operation not permitted’.
As a workaround, it is possible to edit files with PowerShell with [System.IO.File]. However, editing files with UTF requires writing a temp file, so it is way more complex.
When running Cursor as administrator, drive X: cannot be used.
Sorry, I don’t know the previous version number.
The current status is that there is a workaround, which is not obvious and is less efficient. I have yet to test it in full to find if there are any other issues.