The Keep All button does not work and Agent can’t save files automatically anymore.
Second one is not a dealbreaker for me but i’m sick of seeing inline diffs everywhere. After restarting, the issue persists with certain files. These specific files show up as unsaved with inline diff indicators everywhere even if I’m 1000% sure I saved them before closing the cursor and restarting.
The workaround suggested in another bug reports, the Keep All button in the Chat sidebar, only saves the change made in the last prompt. Other changes remain unconfirmed. I’ve tried every advice in others posts about this issue and non of them worked for me..
If there is another solution that I am not aware of, please help me because I have tried everything except removing the cursor and reinstalling it
Can confirm, this is incredibly frustrating and only seems to have popped up recently for me. There’s no way to remove the inline diffs and hover toolbar with keep all. Also makes the “Review next file” button unusable for me as it’s stuck on on file that I can neither accept nor deny, no matter which buttons I press.
Hey, thanks for the report. This looks like a known bug affecting Apply/Accept. The team is actively investigating, and similar cases were reported in 2.0.54–2.0.64.
To speed up the investigation, please provide:
Request ID - after trying Keep All: chat menu (top right) → Copy Request ID
A short screen recording showing Keep All not working and persistent inline diffs
The specific files affected (or confirm if it happens to all files)
Whether it reproduces in Ctrl+K, or only in Agent
I’ll link your details to the existing bug report. Please share the info when you can.
When I close the project folder and cursor and re-login and open the project folder, it immediately shows some open files. Seems like something is stuck in cache. When this happens, the tool does not save the file with the new edit properly. The change on the cursor editor is not even in the local file.
Can confirm I’m seeing the same thing. It’s changes I’ve already kept and commited. Deleted the cache folder - still shows up. Even after starting a new chat and having Cursor re-modify the same line of code (prompting it to modify the same line of code), after accepting the change, the old “stuck” suggestion persist. Very odd.
It’s all stored in the state.vscdb file within the globalStorage directory. This unfortunately has all your cursor login data, etc… I suspect uninstalling and re-installing is just as good as nuking that file. Either one will “fix” this issue. Annoying…
