Short summary
After using Cursor 2.0 and the new model for a while, I want to say thank you first.
Many bugs were fixed and the editor feels smoother, more reliable, and simply pleasant to use.
Cursor was already a great tool that saved me a lot of time, and now it feels even more productive and comfortable.
At the same time, the new version introduced a few serious issues that make daily work harder. I hope this detailed feedback helps prioritize fixes.
What feels better in version 2.0
General product experience
The overall experience became much nicer:
- The interface feels more polished and responsive.
- Everyday workflows are smoother, so it is easier to focus on the actual work and not on the tool.
- The product continues to save me a lot of time, even more than before.
The new model
The new model is very successful. Even when it was still anonymous, I used it constantly.
- In many tasks it is truly impressive and feels like a clear upgrade.
- When it fails or gives a bad answer, it is usually fast enough that I can simply go back in history and recover, so the cost of mistakes is low.
Overall, the model is a strong step forward.
Issues that hurt the experience
I will not open a separate discussion for each bug, since I saw that handling them can take time.
Instead, I will list here the main problems that affect me the most.
Automatic save seems broken
In the recent versions, automatic save feels completely unreliable. This is a very painful issue in day to day work.
Typical flow:
- I make changes in a file.
- I run the checks and see no errors.
- I am happy because everything looks correct.
- Only later I discover that automatic save failed, so the file was never saved and the checks were actually running on the old version.
At that point I need to:
- Find the file again.
- Perform a manual save.
- Rerun everything.
This is extremely frustrating and breaks trust in the editor.
For me, a reliable automatic save is critical.
Update process feels unstable
Version updates used to feel simple and smooth.
In the last several versions, the update process turned into a small nightmare.
What happens now, in almost every update for at least the last five versions:
- I click update.
- Cursor installs the update and closes.
- The editor does not open again automatically.
Then, when I open Cursor again, a worse problem appears:
- It looks like the project is moved one commit back.
- I get a list of files that Cursor claims were not saved.
- The state of the project feels wrong and confusing, as if something in the history was changed.
This behavior repeats across multiple versions and makes me nervous every time I update.
An update process should feel completely safe and predictable.
What works especially well
I want to finish the main part of the feedback with a positive note.
The review tool that lets me walk through all the changes is fantastic.
- It is very convenient and intuitive.
- It saves me a lot of time when checking what changed.
- It turned reviewing my own work into something that is actually enjoyable.
This feature alone adds a lot of value to Cursor for my daily work.
Additional issues with checkpoints and conversation history
Serious bug when going back in a conversation
There is a repeating problem when trying to go back to an earlier point in a conversation using checkpoints.
What I expect
- Choose a specific point in the conversation
- Go back to that exact point
- Only the last few changes should be reverted
What actually happens
- Cursor goes back further than the point I selected
- More changes are reverted than I intended
- I lose work that I did not mean to discard
This makes it very hard to trust the history feature, especially when I only want to undo a small part of the recent changes.
Global effect across multiple agents
When working with more than one agent in parallel, the behavior becomes even more problematic.
Current behavior
- I work with two agents at the same time
- I go back in the history of one specific agent
- Cursor sends all agents back to that same time point
- The other agents lose their later state and progress
This creates a lot of damage, because a local action in one agent affects all agents.
Each agent should keep its own independent history, without global side effects.
Missing way to confirm changes after going back
There is also an important piece of functionality that feels missing in the new version.
Current limitation
- After I go back in history
- If I later decide that I actually want to keep the newer changes
- I have no way to confirm or restore them from inside the interface
In previous versions there was a way to go back and then still approve the newer changes, which made the history feature much safer to use.
Now, once I jump back, it feels like a one way action and this makes me afraid to use checkpoints in complex sessions.
Closing thoughts
Thank you for all the effort that clearly went into Cursor 2.0 and the new model.
The direction is very promising, and most of the changes make my work easier and more pleasant.
If the issues with automatic save and the update process are fixed, this version would feel almost perfect for my needs.