It appears, I suspect in one of the latest updates, a bug was introduced into the change accept/undo process. It now appears that I have to accept (or undo) changes twice now, for them to actually be accepted. Interestingly, after accepting them once, a fainter band highlights the change (dimmer green or red) than in the first pass.
I was confused at first as to why I kept having to review the same files over and over, when I had already completed reviewing them. This has become a rather large-scale time waster…
Steps to Reproduce
Implement changes with agent.
Review changes and accept.
Go back and check those changes again…
Weep as changes still require review!
Expected Behavior
Accepting a change, should accept a change.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. This is a known state management bug in the review system in v2.0.69, and the team is on it. Several users are seeing similar issues with agent change review/acceptance.
To help confirm whether your “double-accept” issue has the same root cause, please share:
Console errors: Help → Toggle Developer Tools → Console - screenshot any errors when you accept changes the first time
File types: does this happen with all file types or only specific ones (e.g., .yaml, .py, .conf)?
Temporary workaround:
Use Git to review changes until the fix is released.
Well, FWIW, I think Cursor updated again today. I’ve been going through accepting changes here, and I don’t seem to be experiencing the problem anymore. If it occurs again, I’ll get you more details. Also, this is mostly with TypeScript (.ts) and JavaScript (.js) code files, but was also seeing it with Markdown (.md, and .mdc for rules), our Prisma schema files (.prisma), and others.