Auto-Accept on Commit setting has not been working and it is SUPER annoying. Also files changed forever ago still have pending changes all over the place

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I frequently just commit changes made by cursor, making the auto accept feature very helpful

Only it hasn’t been working in weeks and is getting very annoying. I don’t know if this is related to the new review changes or what but it is quite annoying.

On top of that, I open files I haven’t edited in days even and there are pending/change diffs all over it with no way to accept them all I even though I have no chats open and I am forced to mash cmd + Y to make them go away

Steps to Reproduce

  1. Make some changes to some files with cursor agent
  2. Commit
  3. Go about normal editing
  4. Eventually come across a file edited from step 1
  5. See a ton of the “changes made” diffs all over the file
  6. No way to accept them all
  7. I have no open chats even (assume i have closed them all since doing stuff in step 3)
  8. No little popup at the bottom of the file (the “got to next file” thing)
  9. Forced to mash cmd + Y on the whole file to make them go away
  10. Even though no changes were made even though no changes were made when I accept them (nothing shows up in git) it triggers HMR/docker watch which is also super annoying
  11. Closing and opening the file doesn’t fix it
  12. Quitting and reopening doesn’t fix
  13. Updating cursor (yes I even tried using a pending update to my advantage) doesn’t fix it

Expected Behavior

like it used to

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the detailed report. This is a combination of several known issues with the new review workflow that the team is tracking.

Similar reports:

Try these temporary workarounds:

  1. For phantom diffs: Copy the entire file CMD+A, CMD+C, press CMD+Z until the diffs disappear, then paste the copied code back CMD+V. This clears the stuck state from workspace storage.

  2. For External-File Protection: Go to Cursor Settings - Agents - Auto-Run, and disable External-File Protection. Sometimes the Agent uses absolute paths that trigger the protection.

  3. Cmd-click for files: In recent versions, cmd-clicking a file should open it directly, bypassing the review tab.

To help the team investigate:

  • Open Help - Toggle Developer Tools - Console and take a screenshot of errors when you see phantom diffs
  • Share the Request ID from the problematic chat (chat context menu - Copy Request ID)
  • Are you using git worktrees or a multi-root workspace?

Let me know if this helped.