“Undo all / Keep all / Review next file.” bug

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi guys. I’m having an issue in Cursor. An agent modified a file, and I can’t remove the usual post-modification message on that file: “Undo all / Keep all / Review next file.” I have no idea what else to try. I even updated Cursor, but the message still persists for that specific file, which is really annoying. Any suggestions? Thanks!

Steps to Reproduce

I can’t reproduce with other files

Expected Behavior

…so that “Undo all / Keep all / Review next file.” disappears when I click on one of those options.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46 (system setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
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.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. This is a known issue with the change review UI state; we’re already tracking it here: 2.0.48: Edit Confirmation UI Unresponsive

Please share so we can add your case:

  • Request ID: chat menu (top right) → Copy Request ID
  • A screenshot of errors from Help → Toggle Developer Tools → Console when clicking the buttons
  • File type and extension, and whether it reproduces only on this file
  • Whether changes are actually applied and saved to the file

Temporary workarounds that helped others:

  • Review and accept changes via the Git tab instead of the review UI
  • In the problematic file, delete the highlighted blocks manually, save, then immediately undo Ctrl+Z
  • Reload the window: Ctrl+Shift+P → Developer: Reload Window
  • Rule out extensions: launch Cursor with extensions disabled cursor --disable-extensions

Let me know if any workaround helps. I’ll attach your details to the current task.

3

Hi Dean,

Thank you very much for the answer.

Temporary workarounds didn’t helped me.

The only solution that worked was to delete the entire local project and then cloned it again from my GitHub repo.

Best regards.