You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System: Ubuntu 22.04.5 LTS (running in Multipass VM on Windows host)
Terminal: xterm-256color
Bug Description
Edit and MultiEdit tools report EPERM: operation not permitted when creating new files, but files are successfully created. The tools show an error message but the operation actually succeeds.
Steps to Reproduce
Just ask claude to create any file with content
Use Edit or MultiEdit tool to create a new file: file_path: /home/ubuntu/projects/my_project/new.txt, edits: [{old_string: "", new_string: "content"}]
Tool returns EPERM error: EPERM: operation not permitted, open '/home/ubuntu/projects/my_project/new.txt'
Check file system - file is created: -rw-rw-rw- 1 ubuntu ubuntu 0 bytes
Use Edit or MultiEdit on same file again - works without error
Expected Behavior
Tools should create files without reporting errors when the operation succeeds.
Actual Behavior
Tools report EPERM: operation not permitted error but successfully create the file.
Additional Context
Environment: Windows host with Multipass VM Ubuntu 22.04.5 LTS
Mount configuration: :C:\projects\ubuntu on /home/ubuntu/projects type fuse.sshfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
Similar behavior observed with bash commands:
echo"content"> new.txt # EPERM error, file created empty
touch new.txt # Successecho"content"> new.txt # Success after touch
This appears to be related to the sshfs mount behavior where file creation triggers a permission error despite succeeding
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
Activity
github-actions commentedon Dec 5, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
github-actions commentedon Jan 5, 2026
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
github-actions commentedon Jan 13, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.