I’ve been using Cursor since the 0.x versions. In the past, I was genuinely excited about every new release — I would literally click Check for Updates almost every day. Lately, however, I feel the opposite: I hesitate whenever I see a new version available.
The reason is simple: almost every update breaks something. If it’s not one issue, it’s another.
Version 1.7 felt relatively solid and stable. But from 2.0 onwards, things have gone downhill — and there are already many posts out there about the problems with 2.0. Right now, I’ve pinned myself to 2.0.69. I did try 2.0.7x, but had to uninstall and roll back because of random issues, such as being unable to connect via SSH. I don’t have the time or energy to debug or file detailed reports for every regression, and as soon as I reverted, SSH worked again. That’s just one small example of the release quality problems I keep running into.
At the beginning, I still reported bugs. But occasional bugs are very different from what I’m seeing now: frequent, repeated issues, and regressions where a bug “fixed” in one version shows up again in a later one. It really makes me question whether there is a proper QA process or any serious testing before a version is released.
As a user, I feel like I’m being turned into a free tester who has to discover bugs and report them so the team can patch them. This feeling is made worse by the lack of clear, timely changelogs at the moment of upgrade (Today - Latest Version 2.0.77 but Changelog 2.0.1-2.0.28: Bug fixes). Updating should be something I do with confidence because it improves my experience. With Cursor today, updating feels risky.
More and more, Cursor gives me the impression of a product that’s being VIBE CODING rather than carefully engineered and released with discipline. I still believe Cursor has huge potential — but without stronger quality control and a more reliable release process, it’s very hard to trust new versions.
