Skip to content

[BUG] Edit/MultiEdit Tools Return False EPERM Errors #3182

Closed as not planned
Closed as not planned

Description

@NikolayMakhonin

Environment

  • Platform (select one):
    • Anthropic API
    • AWS Bedrock
    • Google Vertex AI
    • Other:
  • Claude CLI version: 1.0.44 (Claude Code)
  • 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
  1. 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"}]
  2. Tool returns EPERM error: EPERM: operation not permitted, open '/home/ubuntu/projects/my_project/new.txt'
  3. Check file system - file is created: -rw-rw-rw- 1 ubuntu ubuntu 0 bytes
  4. 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               # Success
    echo "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

Activity

  1. github-actions commented on Dec 5, 2025

    @github-actions

    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.

  2. github-actions commented on Jan 5, 2026

    @github-actions

    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.

  3. github-actions commented on Jan 13, 2026

    @github-actions

    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.

  4. locked as resolved and limited conversation to collaborators on Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:toolsautocloseIssue will be closed automaticallybugSomething isn't workingexternalhas reproHas detailed reproduction stepsplatform:windowsIssue specifically occurs on Windows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions