Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When I generate code changes using Cursor Chat, the Keep and Undo buttons are missing most of the time.
In those cases, the changes are automatically applied to the file without giving me the option to review or undo that specific change.
Additionally, when I click the return icon in the message and select “Discard all changes up to this checkpoint?”, then click Continue, the changes are not reverted properly to that checkpoint.
This happens intermittently:
- Sometimes I see Keep/Undo buttons.
- Most of the time I do not see them.
- When they are missing, changes are auto-applied and difficult to revert precisely.
This makes it risky to use Cursor for production work because unintended changes cannot be easily undone.
Steps to Reproduce
- Open any project in Cursor IDE.
- Use Chat to generate or modify code.
- Observe that in many cases:
- Keep / Undo buttons do not appear.
- Changes are automatically applied.
- Click the return icon in the chat.
- Select “Discard all changes up to this checkpoint?”
- Click “Continue”.
- Notice that the changes are not properly reverted.
Expected Behavior
- Keep and Undo buttons should always appear after Agent generated changes.
- Changes should not be auto-applied without explicit confirmation.
- “Discard all changes up to this checkpoint” should correctly revert all changes made after that checkpoint.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
IDE:
Version: 2.5.20 (system setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200
CLI: Not used
For AI issues: which model did you use?
I am using “Agent” with Auto mode
Additional Information
- This issue occurs intermittently but frequently.
- It affects normal development workflow.
- I am using the latest stable version of Cursor.
- This behavior was not consistent in earlier versions.
Does this stop you from using Cursor
No - Cursor works, but with this issue
