UX/UI confusion on restoring checkpoints

[charles]

The “Restore checkpoint” button appears in the question, and it appears to restore the checkpoint as of when the question was completed, not when the question was started. In a visual timeline its very confusing. if I want the code thats after all of the LLM saying “I made this change, that change, and the other change” i have to click the restore button BEFORE all of those messages.

Realistically the UX was far far better before when restore and stop and such were not in the input boxes, but above it in the timeline. It made far more sense. Please revert to that, its much clearer as to what you’re asking for and what you’re going to get.

Check the forum to ensure the issue hasn’t been reported already
Provide a clear description of the bug
Explain how to reproduce the bug (if known)
Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Tell us if the issue stops you from using Cursor.

[yurkomik]

i am not sure I understand. Do you mean prompt?
I do agree that it was better some time ago when you could undo any change in the middle of the execution, e.g. you see agent did right in 1 file but than started doing some strange things in 2 other files you could stop it and undo two last file edits but leave the first one. now you have to discard all work done.

[dwarka39]

This is actually terrible wtf? You can no longer restore checkpoints at certain points during the process, only with each prompt. That is… bad. I downgraded back to an old version, I don’t see how anyone can use the new UI is that doesn’t change.

[dwarka39]

Brother this is not just that “it was better”… this is like… detrimental.

“now you have to discard all work done.”

Think about that statement… like how is this even a thing? How did the Cursor team not consider this? I don’t get it.

[yurkomik]

Yes, I see what you are talking about. Their designers should learn about mental models. 1) you can’t invent new models without reason 2) you should not change established models 3) if you have to change models make sure you educate users. It’s super confusing that rerunning prompt does different thing than clicking “restore” checkpoint below that prompt, and that clicking on text below prompt does other changes. It’s not intuitive. I hope they’ll fix it.
If anybody from the cursor team wants design help, let me know. I run Cieden UX design Agency and can demo some you Ideas on how to improve Cursor UX.

[danperks]

Hey, you can access intermediate checkpoints by clicking the small + symbol that shows up on hover between each step, like so:

This will rollback to this point and, if you want to continue, you can write your message in there to carry on from wherever you choose.

[dwarka39]

Unless I’m mistaken, the difference is that you’re forced to enter a new prompt to fully revert to that point, because clicking outside of it will undo it. Where as with the old version, you can “Restore” to a certain code block without being forced to write a new message. The new version with the plus sign felt so awkward that I uninstalled and went back to 4.5.14.

[danperks]

Thanks for the feedback, I agree just jumping back without a new message is not straightforward with this method, will feedback to the team!

[dwarka39]

When you say “not straightforward” do you mean it’s somehow possible? If so, how?