I have been getting “Accept Editing” request to edit he files multiple times per day, very very annoying.
-It is inside the project, i also disabled all “prevent from editing” options
-It was working fine before Cursor 2.x
-It sometimes doesn’t ask, sometimes asks, confusing
-I don’t have any agents editing this file, only ONE chat active(open)
Steps to Reproduce
Just regular working on a project, it will ask suddenly
I set it to Run Everything, turn off all file protections, still it is not fixed, asking permission to edit files, i deleted project and cloned repo again, still same. Have smn reported this issue or am i alone at this one?
Hey, thanks for the detailed report and screenshots, @mkuprionis, this confirms the worktree bug we’re currently tracking.
Your screenshots clearly show the issue: Cursor is treating files under .cursor/worktrees as Cursor configuration files, which is why it’s asking for permission even when “Run Everything” mode is enabled.
To help the team fix this, could you please share any console errors that appear when the permission prompt shows up?
Thanks for the detailed reports and console logs, @mkuprionis, that’s really helpful! And thanks for confirming, @Mark_Feighery.
This is a known worktree-related bug we’re tracking.
Cursor is incorrectly treating files under .cursor/worktrees as Cursor configuration files, which is why it’s asking for permission even with “Run Everything” enabled.
@mkuprionis, your console errors confirm the issue, including TypeError: i.with is not a function and path resolution problems with worktree files.
Temporary workaround: unfortunately, the current options like “Run Everything” mode or disabling protections don’t fix this.
I’ll pass these latest console errors from version 2.1.32 to the team.
I am experiencing the same issue still. Report below;
Bug Report: Auto-Accept Still Not Working in 2.1.39
Environment
Cursor Version: 2.1.39
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
OS: macOS Darwin arm64 25.1.0 (Apple Silicon)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
Issue Description
File edits require manual confirmation (pressing Enter) after each change, despite having “Run Everything (Unsandboxed)” mode enabled. Previously, changes were auto-accepted without any key presses.
Current Settings (Verified Correct)
Auto-Run Mode: Run Everything (Unsandboxed)
Auto-Accept on Commit: ON
External-File Protection: ON
Dotfile Protection: ON
File-Deletion Protection: OFF
Browser Protection: OFF
Expected Behavior
With “Run Everything (Unsandboxed)” selected, file edits should be applied automatically without requiring manual confirmation.
Actual Behavior
Every file edit prompts for confirmation and requires pressing Enter to accept, even for files within the workspace that aren’t dotfiles or external files.
Steps to Reproduce
Open any project in Cursor 2.1.39
Ensure Auto-Run Mode is set to “Run Everything (Unsandboxed)”
Start an Agent conversation that makes file edits
Observe that each file edit requires pressing Enter to confirm
Additional Notes
This worked correctly in previous versions (pre-2.0)
Toggling External-File Protection and Dotfile Protection OFF does not resolve the issue
Restarting Cursor after changing settings does not resolve the issue
Thanks for the info! This is a known bug with file handling that is already being tracked.
Even in “Run Everything (Unsandboxed)” mode, Cursor asks for confirmation for every file - this is due to incorrect file path handling, especially in worktrees.
Quick checks:
Are you using git worktrees?
Open Help → Toggle Developer Tools → Console and share any errors
Try disabling all protections: Cursor Settings > Agents > Auto-Run > turn off External-File Protection and Dotfile Protection
@deanrie, we’re experiencing the same problem. Even with Auto-Run Mode set to ‘Run Everything (Unsandboxed)’ and with External-File Protection and Dotfile Protection disabled, Cursor still asks for permission before modifying files. This isn’t just a worktree issue for us; it also occurs when I’m using local agents.
Having a similar issue, but for creating new files.
When the AI assistant creates new files during multi-step operations
(e.g., TODO-based tasks), the ACCEPT button that should appear below
the file preview card intermittently fails to render. This forces
manual file creation via copy-paste.
The button renders correctly during simple, single-step operations.
Environment:
OS: Windows 10 (Build 26220)
Cursor Version: [your version]
Reproducible: During AI multi-step/TODO operations
Expected: ACCEPT button should always render for file creation approval
Actual: Button missing during complex multi-step operations
After the new Cursor update (2.1.49), a major bug appeared for me, when agent creates new file, it waits for my approval, i cant either opens the file bcs its still didnt been applied, and i cant also accept the edit, that keeps it forever waiting
