I noticed that when Cursor generates code changes, the diffs seem to already be applied to my files immediately even before I click Keep. For example, if I rebuild my app, the new changes are already live, even though the UI still shows an Keep/Undo prompt. Is this unintentional or is there a reason or why the decline is functional but the Keep isn’t doing anything besides acknowledging the changes that are already made?
Hey, thanks for the report. In Review mode, Cursor shows diffs and lets you accept/reject changes at the file/line level. “Keep” confirms the current edits and exits review mode, “Undo” rolls them back. More details: Review | Cursor Docs
If Keep doesn’t remove the highlighting/review mode for you or the behavior is different - this could be a bug. Please share:
- Cursor version (Help > About) and OS
- Steps to reproduce and a short video/screenshots
- Errors from Help > Toggle Developer Tools > Console
Let me know if this helps and if there are differences in your scenario.
Thanks, this makes sense. So when Cursor makes code changes they are already applied but I have the option to remove them with Undo. I interepreted the changes to be tentative / not applied until the user clicks Keep/Undo.
Great, glad we cleared that up. Yes, the changes apply immediately, and in Review mode, you can either confirm them (Keep) or revert (Undo).
1 Like