I noticed I use the following pattern pretty often.
I ask the agent to do some temporary workaround,
just so I can test something out.
So I also ask it to add uppercase comments all around it to make sure I don’t approve it by mistake later.
What if there was a “temporary change” feature that will make sure changes like this have only an “Undo” option without a “Keep”?
Hi @Noam_Kleiner Thanks for the feature request! We actually already have a feature built that’s pretty aligned with what you’re looking for, and that is the checkpoint feature. You can use this button to undo the changes that have happened after this point. So you can scroll up to the point in your chat history that you want to undo and then press this button.
50% of the time this is highly unreliable though! sometimes only some changes get rolled back, espcially if you have done any manual changes to the files the agent edited.
Using git for the same functionality is much better, but you have to remember to do it. E.g. every time before you start chatting, make sure there’s no uncommited changes, then commit after every step. This is also a very good dev pattern and 10x more reliable than what Cursor built unfortunately. Once you start doing that it becomes second nature.
Thanks for the reply! Yes, Git is always recommended as a more robust option for version control of your code. You could always set up a skill to make git commits easier and more repeatable!