The allow access to external files ‘workaround’ seems to solve this, if you’re happy with the risk whilst they figure this out.
Yep, I’ve enabled it temporarily, but I’m definitely not happy with solution, even as a workaround.
1 Like
Me too. Request ID: 6278533b-cd01-4a9f-a5d7-6387a6d0ed24
This is an issue if you are using a workspace file. I started using a workspace file so i can keep two related repos open at the same time, but it started to ask for approval of every file edit in either repo. I suspect its because it is using absolute paths under the hood instead of relative paths, to distinguish between repos and so it triggers the “External Files” rules. When i “Close Workspace”, i then opened one of the repose as “Open Folder” and the problem went away. Please fix the workspace issue, thanks
1 Like
This is my experience as well. The problem has been somewhat intermittent but I would say the majority of the time for the past few weeks, across many cursor updates, it has been asking me for approval of changes it shouldn’t need approved. Changes to the agent permission settings did not help in my case. I use workspaces a lot, for things like coordinated development across frontend, middle tier, and backend. And some of our projects call each others’ services or use shared internally developed packages. So I would put overlapping sets of whatever needs to be worked on together in workspaces. What fixes the issue for me is putting symlinks to outside packages or services and then just opening one parent directory as a directory, not as a workspace. I like the fact that the set of recent agents switches when you switch workspaces, and I was worried I would lose that with this approach. But it seems like the “set of recent agents” feature works just as well with opening directories and opening workspaces. I’m not sure what other functionality if any I’m losing by not using workspaces but so far I haven’t noticed any. So for my fellow cursor users experiencing this: use directories not workspaces. For the amazing cursor team working on this: set yourself up with a workspace with several directories in it when you’re trying to reproduce. One thing I would like to experiment with but haven’t yet, is whether it matters where the workspace is saved for this bug. Like, if I have workspace listing directories a/1, a/2, and a/3, my normal pattern because of the way I build up projects is that the workspace is at e.g. a/2/x.code-workspace. Does it help if instead it’s at a/x.code-workspace? It shouldn’t of course but just for the purposes of understanding this bug.
Constantly asks for approval to edit files while using the worktree and parallel generation feature on windows wsl with the project located in wsl. Completely defeats the purpose of that feature when you have to go to each individual generation and hit approve for every single action. It’s been like this for a week. It’s either a bug with it not recognize ~/.cursor/worktrees as part of the workspace or it thinking that the file within ~/.cursor/worktrees is restricted. Toggling off external file protection makes no difference for this.
Could you try updating to 2.2.36? We’ve patched it on this release for worktrees.
Still happens on latest 2.2.36:
This is with “External-File Protection” disabled as well, Auto-Run mode is “Run Everything”. Project is located within WSL home i.e. ~/folder/project, and the worktree it creates is under ~/.cursor/
Thanks for this, taking a look
1 Like
auto approve not working :
Version: 2.2.36 (user setup)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045
does not work solution to enable editing for external files. I really tried not to update , but it “force updated” and it spoils my workflow .
maybe , just maybe - you could make some LTS or similar version that updates only when features are tested , not just Vibe coded and f* it ship it way 
@Ronalds_Sovas sorry there was some internal miscommunication and only 2.2.37 has the fix for this bug on worktrees. It looks (from this thread) that there might be a more generalized version of the Accept/Reject bug showing up that doesn’t have anything to do with worktrees.
1 Like
The latest update did not fix it for me on worktrees. I’ve uninstalled cursor windows, wiped app data cursor folders, wiped .cursor, wiped ~/.cursor within WSL, then reinstalled and the same thing happens.
request id: 9c9a2203-fe86-4434-8dd5-fc4a02fac127
Version: 2.2.43 (user setup)
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Thank you @cxmplex , I have just verified that the fix isn’t Windows compatible. The proper fix is indeed coming in the next 2.3 patch release.
1 Like
Thank you, look forward to it. And to clarify mine is windows cursor but connected to WSL using the remote plugin, so worktrees are in the ~/.cursor folder and the project is in ~/work/project while Cursor itself is running in Windows.
Is it just me, or is it still not improving? It’s a window.
I’m also experiencing this on Version: 2.3.29 on Mac
Just got back to work from the break and this is quite annoying. I have to approve every tiny change before I can even see it for review
Solution:
Ok I figured out what’s going on. The agent is able to edit files in the workspace, and in the pre-defined .cursor folders (rules, commands, etc). But it’s not able to edit files in custom .cursor folders (ie. .cursor/my-projects).
omg, this is so freaking annoying. I had to accept every single one of these changes individually before cursor would continue. I used to be able to walk away from my computer and let cursor work, and now it can’t go more than 10 seconds without me
Is there not yet a fix for this?
TWO-STEP ACCEPTANCE WORKFLOW:
Cursor currently requires a two-step process for reviewing Agent file changes:
- First: Click “Accept” to view the changes in diff preview
- Then: Choose “Keep” or “Undo” to finalize the changes
I don’t understand why its necessary to allow Agents to create or modify files outside of the workspace automatically to stop a two-step acceptance workflow inside the workspace.
I can confirm this happens to me as well. I’m on macOS and if I open a workspace in cursor, even project in that workspace runs into this problem. If I open a folder in that workspace the problem goes away.