Hey, thanks for the report. We’ve seen similar reports from other users recently.
A couple of things to check:
Single file case: If the agent only changed 1 file, the Undo All / Keep All buttons are hidden by design. You should still see per-file Undo / Keep buttons though. Can you confirm how many files were in the changed files list when this happened?
Try these workarounds:
Ctrl+Shift+P > Developer: Reload Window
Close and reopen the chat where the agent made changes
Run cursor --disable-extensions from a terminal to rule out extension conflicts
As a fallback, use the Git panel to revert unwanted changes
If it still happens, can you send:
A screenshot of the review panel when it occurs
The Request ID from the agent run (chat menu top right > Copy Request ID)
The team is aware of this issue. Your report helps with prioritization, let me know how it goes.
Having exactly the same issue here and it makes this version completely unusable. Have tried all the steps above and none have worked. Git compare is not really viable solution. Would just like it back the way it was in previous version.
Not even 1 hour into switching from vscode/copilot, and I was regretting it. Where is the “keep” button? I’m being micromanaged to death with an unintuitive, broken file management proxy.
** Update: I downgraded to 2.3, which corrupted my previous chat, and now I get to burn through more tokens just to see if I can even continue with Cursor. Also things are changing so often that even Grok and Claude are having difficulty giving relevant advice. I’ve burned through about $4 over 4 hours and have accomplished nothing but a bad taste for Cursor…
** More Update: 2.4 seems to be tolerable (so far).
Hey everyone, we can see this issue is still happening for a lot of users. This is a known bug with diff rendering, which is why the Keep and Undo buttons don’t show up.
For now, the most reliable workaround is to make a git commit before each agent session. If anything goes wrong, you can roll back with git checkout -- . or use git stash.
@Jeff_Hill, I get that this isn’t a great first experience. Version 2.4 is definitely more stable for this, and I’m glad you found a working option.
I do appreciate the response. That said, over the last week Cursor has been opening every planning md file (in an unsaved state for some reason) every time the agent starts a new plan. And not 10 minutes ago the last mass opening caused a crash and seems to have lost a week-long (current) session. The extended plan billing is getting a bit much as well (considering the app’s bugs).
