So i’ve been on 1.7 for a while as it was stable and I got to know it inside out. And all I read about 2.x is that it is full of bugs and in some cases unusable. But now, this morning, I get a message
“Please update to the latest version of Cursor at Download · Cursor to continue using the Agent
(Request ID: cb40d59e-fb1e-4f4d-a9c3-004991669d65)
”
Yikes. We’re 75% into a large project and always planned to upgrade once this was done but being forced to now kinda sucks (small dev team with 2 x Ultra licences). Why is this upgrade being forced now - unless it is something to do with Claude API crackdown?
This is the same issue I am facing. How did you resolve it? I was using prompt cursor-agent to get my chat interface. Now nothing working. I didnt even get a note to upgrade.
I think it is completely reasonable to deprecate old version of any program, especially if it consist of any security vulnerabilities and other major imperfections.
Latest stable release has some bugs, yes, but it does not break your current flow. You can still use it just fine and finish your project. There are some new features that are buggy and if you come across one, just do not use it. The core functionality works just fine and is rather stable.
Old versions of Cursor (including 1.7) no longer support Agent due to critical security updates and architectural changes. This was a planned end of support, not a sudden decision.
About 2.x stability: the latest version 2.3.23 is much more stable than early 2.x releases. Several users in this thread confirm they’re using it without issues. Most bugs from early 2.x versions have been fixed.
I’d recommend updating to 2.3.23. Core functionality works reliably, so you’ll be able to continue your project. If you hit bugs in new features, just avoid those features. Basic functionality isn’t broken.
If you run into specific issues after updating, describe them here. We’ll help sort it out.
My issue is i am NOT running on local env. I have this all running from cloud vm so its been very difficult to update. I wish I had warning in the system as well would save me time.
Not fair, I transitioned only over Christmas, there is some learning curve 1.7→2.x and I was in a work sprint and had no time for non-sense.
Used 1.7 / opus 4.5-high. It managed my server without single hickup. 2.2/4.5 opus broke my server on second operation I did with it…
…once you start relying on these tools in real work and have some good alignment with the model, the stochastic nature makes switching a bit tricky.
So hold your horses cowboy these things are moving into production/professional work-flows and cursor is a bit wild on bad upgrades and should get the feedback.
Does the latest version of Cursor support all the functionality of 1.7? Last I heard, Cursor 2.x had removed the ability to reference git commits, for instance.
I would highly recommend upgrading to Cursor 2.0. For git commits, you should just ask the agent - it is significantly better than the mention menu. The agent can read parts of commits, list files, etc.
I did upgrade to 2.0 and it could not reference git commits anymore. If I mentioned a git commit, the Agent would struggle and struggle to try to read them with command line tools and ultimately fail after wasting many more tokens. So I downgraded and disabled updates. Now we’re being forced to downgrade to 2.x?
cursor 2.X include 2.3 is compelety broken,always stuck on “planning next move“, and agent become stupid. Dont trust those people say cursor 2.3 is “ all system running“. I’m tired of using cursor 2.3.
these things are moving into production/professional work-flows and cursor is a bit wild on bad upgrades and should get the feedback.