Within the same chat, going back to an earlier edit pill and sending a new message from there, showed a popup whether to revert or keep changes before continuing (popup is also only accessible by mouse grrr!).
It has a checkbox on the left side to not show that popup again.
BIG problem: I checked it and clicked the option to NOT revert any changes.
BUT now I can’t get that popup anymore and it REVERTS everytime any changes across several files!
This almost gave me a heart attack loosing hundreds of line changes being reverted!!! I had to manually go through each file’s “Timeline” to recover their content!
There is no obvious option in the Cursor Settings to revert that checkbox and get the popup back! This should be easy to find, but it isn’t!
I hope the devs @danperks can fix this asap, please!
Please, is any dev reading this and could confirm?
This issue still persists in 0.48.2 and Cursor is still reverting all changes made “below” a chat pill without confirmation for me.
I don’t want to fully uninstall Cursor with all the config I’ve done just because noone can tell me where to find this setting so the popup shows up again. Please help, thank you!
As far as I can tell there is no option via the UI to reset all configs/dialogs. And the preference isn’t stored in the settings.json so you cant just modify that. You actually need to modify the SQLite database file used by Cursor (and VS Code) to store this kind of state, here is how:
Locate the file: For me it was the state.vscdb file in C:\Users\<NAME>\AppData\Roaming\Cursor\User\globalStorage folder
Backup: Strongly recommend backing up the SQLite file before making any changes. Direct modification can easily corrupt your application’s state. Just copy and paste the file in the same directory to get a state - Copy.vscdb.
Close Cursor completely.
Open/connect to the file in an SQLite editor, I used DBeaver
Navigate to the ItemTable table and search for dialogDontAskAgainPreferences or submit-from-previous-message, mine was under the the src.vs.platform.reactivestorage.browser.reactiveStorageServiceImpl.persistentStorage.applicationUser key
Carefully modify the JSON value for just that key, changing {"submit-from-previous-message-2":true} to {"submit-from-previous-message-2":false}
THANK YOU so much!! It worked!
DBeaver barfed with out of memory, so I used UltraEdit to edit that file (with backup in place) and now the popup is back.
Such an option is absolutely a must have to be “in the open” to be able to toggle it, Cursor team!
Still present in 0.47.8: I checked “Don’t ask again”, pressed “Continue without reverting” and now Cursor is doing the opposite (reverting all changes without asking).
Yes I’m having this same issue. Frankly, this is a HORRIBLE feature. I don’t know why this was added in the first place.
I frequently edit previous messages in a chat, and having all my files reverted with no way to restore them is such a bad user experience it’s not even funny. There is no obvious way to disable this feature. This has made Cursor unusable for me.
I suggest using the Local History extension which can keep several versions of your files in a .history folder (add it to .gitignore/.cursorignore/.cursorindexignore so its not used by AI) and can restore them if a change happens.
Myself i use revert regularly when i dont want to keep changes AI made. On complex issues it sometimes misunderstands and applies the wrong fix, so instead of having to fix the file myself or make the chat longer by asking AI to fix it, i just edit my previous prompt to prevent it from misunderstanding and press revert changes.
However you are not required to use it and you can disable it permanently if you look at the keep/revert dialog in 0.48. by clicking Dont ask anymore.
You’re missing the point here: the “Don’t ask anymore” is NOT storing the CHOSEN action, but plainly defaults to REVERT, which is the catastrophic part.
Just upgraded to 0.48.6. I still don’t see any modal open up or anything in the settings; it still just reverts all my code when I edit a prior message.
When will this be fixed??? This is making Cursor almost unusable for me. I have to do stupid-■■■ ■■■■ like copy over my messages and create a new chat just to work around this garbage ‘feature’
Ok thanks, I see the dialog now. However, this doesn’t feel like a satisfying solution. I don’t want to deal with this modal every time I edit a previous message. It gives me anxiety incase I mis-click it.
Reverting all of my code across multiple files just because I edited a previous message is very user-hostile. I very frequently edit previous messages to manage the model’s context. Chat is the primary feature I use. Just a simple checkbox in settings to never revert my code when editing a prior message would be super helpful.
Completely agree. The consequences are terrible because reverts cannot be undone. This is a non-obvious footgun that detracts from the product. Re-enabling the dialog is a small bandaid, but the Cursor team should make the following changes to solve this issue for good.
Replace “Don’t Ask Again” with “Remember My Choice” so that users who never want to revert changes can skip future pop ups.
Revert should be the exception, not the norm. Users can undo to unwind code changes. Going back to previous messages is the only way we have to prune conversation branches in our context window. It seems like a big assumption that users pruning a chat also want to unwind code from that branch. Chats and code inherently have different degrees of temporalities!
When you select “Don't ask again”, and then press “Continue without reverting” it will then always revert going forward, which is exactly the opposite of what you’d want.
The expectation is that “Don't ask again” will always do whatever option you select:
"Don't ask again", “Revert” should mean “Always revert”.
“Don't ask again”, “Continue without reverting” should mean “Never revert”.
Right now, no matter which option you select, if you use “Don't ask again” it will “Always Revert”.
Personally, I never ever ever want it to revert.
For me, the popup might as well say “Permanently throw away a lot of work with no option to undo”. I know other people may have other workflows… but for me, the fact that we even have this option is terrifying. The fact that it defaults to reverting is terrifying. The fact that it isn’t accompanied by a bright red flashing warning is terrifying. I mean… why do we even have that lever?
Yeah. To be honest, it blows my mind how reverting users’ code was even considered a good idea, much less pushed to prod and shoved in users’ faces as a ‘feature’. And the ‘fix’ we get is pretty much a crappy bandaid. This makes me question if the Cursor team actually knows what their users want.
LOL my coworker just got screwed over by this too and lost his entire day of work. Please never push such a terrible ‘feature’ again without at least an option to permanently disable it
I am actually that coworker and I made the mistake of trusting in cursors ability to revert changes it applies and after using prompts to attempt to revert and attempting to use a checkpoint I lost an inordinate amount of progress and my code is currently a mess. Anyone using this please always commit your work before attempting to engage with any type of assistance it provides.
Backup: Strongly recommend backing up the SQLite file before making any changes. Direct modification can easily corrupt your application’s state. Just copy and paste the file in the same directory to get a 
