Checkpoints are no longer added before each code change.
Checkpoints are sometimes added only at the very beginning of the request (or ends). And in version 0.45, checkpoints were added step by step, after each action of the agent with the code. It is impossible to use checkpoints now. I’m very upset.
It’s a pity that version 0.45 is not available, it was much better than 0.46. ;(
Issue stops me from using Cursor.
38ea7eca-192c-4653-bcb7-1bdf760043e4
Win10
Hey, yes, you’re right. Now, checkpoints are added at the very beginning of the request. I think now it no longer works as before.
I think Checkpoints is the most important feature for AI-coding
Even web coding platforms started to add it.
What was the idea behind removing it ?
I fully support you.
When the AI starts going in the wrong direction, you can roll back one step at a time. Stop at a point when everything was still fine and continue on. I did this all the time.
Now I have to roll back completely. This is especially frustrating when Composer has already taken 10-20 steps.
The functionality has changed a lot, but it is still there. The UI is just really hard to discover.
If you hover on the space between replies, a TINY “+” button will appear. If you click on that, you can add a new message and revert from just that point forward (similar to the old checkpoint flow).
IMO, the UI needs to be more discoverable and accessible (hover to discover needs to disappear, and larger buttons for those of us clumsy folk).
Thanks for sharing! That sounds like a baffling change of UI, I really wonder what the logic was behind thinking that would be an improvement?
Unfortunately, this is only a partial solution to the problem. So I can’t activate the checkpoint to see what happened. Previously, I could just go through the checkpoints one by one to find the place where the AI started making mistakes.
