Keep/Undo blocks stick around for a long time

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Sometimes when opening files for editing, large chunks of code that I accepted days or even weeks ago will be in the highlighted “keep/undo” state. Happens very often and makes the IDE pretty much unusable because it’s easy to lose track of what my agent is actually working on.
If I accept the changes, the file doesn’t actually change and no changes are shown in version control because as I mentioned, these code blocks were accepted already.

Steps to Reproduce

Accept code changes from the agent, then re-open files that were edited.

Expected Behavior

Cursor should remember that I accepted these code blocks WEEKS ago and stop prompting me to keep or undo them.

Operating System

MacOS

Version Information

Version: 2.4.28
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Sonnet 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known issue with the review UI. The keep and undo blocks don’t get cleared after acceptance, and files keep piling up. The team has already worked on a fix, but based on your version, it looks like the issue is still happening.

Try these workarounds:

Quick ones:

  • Close and reopen the specific chat (sometimes this helps temporarily)
  • Cmd+Shift+P → Developer: Reload Window

If that didn’t help:

  • Make any small change in the file, then stage and commit it. This can “wake up” the Keep All button
  • In the problematic file, delete the highlighted blocks, save, then immediately press Cmd+Z (undo)
  • Rename the file, fully close Cursor, reopen it, then rename the file back

I get that this is annoying with lots of files. If the workarounds don’t help, can you send the Request ID from the last Agent request (chat context menu → Copy Request ID)? I’ll check if we need to escalate again, since there was a fix but it clearly didn’t cover all cases.

Related threads with a similar issue:

Thank you @deanrie , unfortunately none of those workarounds cause the stale blocks to disappear.

Last request ID: `72909805-d0c4-4806-a793-ad0c0574f026`