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 (…

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 proj…

Hey, thanks for the question. 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 relea…

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.

I have been on 1.7 for a while and am not willing to be subjected to to most ridiculous, amatuer release cycles of any software there has ever been. What a ■■■■ show

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…

@mwjt42 It isn’t. the agents are literally not able to read or edit any files, making the entire point of the app mute. I suspect it happens when they added their own commit system, but trying to troubleshoot myself hasn’t come up with a definitive cause.

[image] liquefy: Latest stable release has some bugs, yes, but it does not break your current flow. How do I even put this… [image] mwjt42: because they don’t happen to support your decision of sticking to an outdated version is totally uncalled for. v1.7 is better than versions 2.0-2…

I just got this error, too. :frowning:

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.

Wait... Cursor 1.7 Now No Longer Works At All?

Discussions

Michael_Shane (Michael Shane) January 11, 2026, 3:31pm 9

How long do they normally take to anser?

Topic		Replies	Views
I’m increasingly afraid of working with Cursor (stability issues) Discussions terminal , auto-run	13	694	February 26, 2026
Cursor forcing an update - I want to stay on old version Help	20	998	February 23, 2026
Each new update is unpredictable Feedback	30	3390	August 18, 2025
Cursor 2.3 is here! Release Discussions java	53	15565	January 19, 2026
Bad update this morning Bug Reports	28	2854	July 27, 2025

Wait... Cursor 1.7 Now No Longer Works At All?

Related topics