Reverting code when editing prior messages is HORRIBLE

Feedback
1

When I edit a previous message in a chat, there used to be a confirmation pop-up on whether to revert my code up to that point, or keep it as is. I pretty much never want to revert it, so I selected the option to do so and checked “Don’t ask again”.

Now, it always reverts my code when I edit previous messages in a chat, and no confirmation pop-up shows up. I can’t even ctrl+Z to undo the file to the previous state – WTF??? And it does this across multiple files. The only way to retrieve the previous state of my files is going in VSCode’s local save history.

Frankly, this is a HORRIBLE feature that should never have been added in the first place. I never want my files reverted like this. There should be an option to never have my code reverted in the settings, but no such option exists.

I and many other users frequently edit previous messages in a chat. I expect my code to stay as is when doing so, and not be reverted. I have lost hours of work over this.

Over the past few months, Cursor has become very opinionated in its features. I don’t care about Agent and Composer, all I ever use is chat, especially since I’m working on a large >200K LOC codebase. Certain ‘features’ like this are extremely questionable. Please prioritize a minimally disruptive experience for your users.

This has made Cursor unusable for me. I am strongly considering canceling my subscription and switching to other competitors with a less disruptive user experience. Please fix this ASAP.

1 Like
2

You seem to have posted this already in another thread i saw. :slight_smile:

I aded there a comment with two other options you can use to prevent it.

I think overall Cursor team made the right decision by allowing it and you can disable it if you dont want it.

3

Sorry don’t know what you mean? I updated to the latest version. When I edit a prior message in a chat, I still don’t see any keep/revert dialog pop up. And I don’t see anything in Cursor settings to bring the dialog back or disable this entirely

4

That feature might be likely new on 0.48 that is rolling out and fixing a lot of such issues.

I assume you are on 0.47 or earlier, is that correct?

5

Ok I see, I’m still on 0.47.8. Didn’t realize 0.48 was rolling. I attempted update and 0.47.8 is what it set me to, so I guess I haven’t been rolled out to yet

6

No worries, yes its going to be available.

However if you need this change urgently you can use the Early Access option.

7

By available do you mean the confirmation popup will show again? Or will there be an option in settings to permanently disable this? I don’t see that mentioned in the changelog

8

Yes i have both but if this does not show there is following option a user has tried.

9

hey i have the same problem here, can someone point to that other thread so that i can solve it aswell