I’m terrified of any new update, because everything that was working now simply becomes unusable! UPDATES MAKE THE CURSOR EXTREMELY UNPREDICTABLE! WORKING WITH THIS PROFESSIONALLY IS A NIGHTMARE!
YOU NEED TO BE PROFESSIONAL AND APPLY METHODOLOGIES BEFORE DEPLOYING A NEW VERSION INTO PRODUCTION! IT’S UNACCEPTABLE THAT YOU DON’T APPLY UNIT TESTS, AT LEAST!
Steps to Reproduce
VERSION 1.3.6
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
I wholeheartedly agree. And why are there new updates being pushed EVERY DAY. Is there something wrong with my Cursor or are there really that many new updates? It’s confusing because the “New Update Available” banner tells you nothing about what is the update, or even what version it is.
This is extremely distracting. I love Cursor as a tool, but if I have to constantly interrupt what I’m doing because of this banner, its difficult to stay in the zone and enjoy “the vibe”.
Totally agree with the original poster, actually that is why I came here. It’s unprofessional to ship updates every day, especially since its a Kinder surprise update.
It’s even worse. I updated from 1.3.5 from 1.2.4 and could not start a chat at all. On their download for 1.2, I got 1.2.1, while 1.2.4 is the current 1.2. It worked though.
Some people reported that 1.3.5 worked great for them, while 1.3.6 does not, which works for me!
Totally unacceptable for a professional tool that people rely on for their jobs and livelyhood. BETA CHANNEL, USER FEEDBACK, QA!!! simple stuff. stop pushing out ■■■■ and just focus on making this stable. No new features until its rock steady and there are no more bugs to fix.
pretty obvious that they are using AI too much to develop cursor and have forgotten how to think for themselves. bunch of junior vibecoders just pushing out AI slop code on the daily. QA guys, double the size of your QA team and don’t lean on AI so much.
1.3.x was mistakenly pushed to some non early-access users, and had some problems, which has caused some loss of confidence, but was clearly explained (and apologised for) in the forum.
Patch notes up to 1.3.8 exist in the changelog (although we’re currently on 1.3.9)
I completely agree that future early-releases should have a separate changelog, or in-app notification, rather than a “guess what’s new” discussion in the forum.
@condor is this a request that’s already being considered, please?
Perhaps the app itself should include ‘pre-release’ or ‘stable’ in the about/title bar or somewhere to set expectations.
1.3.x was mistakenly pushed to some non early-access users, and had some problems, which has caused some loss of confidence, but was clearly explained (and apologised for) in the forum.
I am a non-early access user. I am on 1.3.7. Does that mean I am on the beta, or is 1.3.x the official version? Edit: I read that 1.3 shipped on July 27th, I guess its official now, and I was one of the lucky guys who got it early
Patch notes up to 1.3.8 exist in the changelog (although we’re currently on 1.3.9)
I had no idea that the patch version release notes where nested there. I guess now I know. Just a suggestion maybe make it more clear where the release notes are,
Perhaps the app itself should include ‘pre-release’ or ‘stable’ in the about/title bar or somewhere to set expectations.
I think that is a great idea. About tab is where I went to look when I started investigating this constantly recurring “Update available“ banner.
I really love Cursor. I think that it is quite amazing what it can do so I want to root for you guys. But please I implore you, slow down the release cadence. Consolidate your maintenance releases, there is no need to ship a new release for each bug fix. Do it biweekly if you absolutely have to ship often, not every day.
Every time I surpass a limit ($), cursor reminds me, then obliterates my context, summarizes the session in a new chat, and basically lobotomizes the agents I was working with. This is extremely counterproductive new behaviour. Super not cool.
much appreciated. In the final stages of bughunting/QC/QA of a complete app and solving complex async calc flow issues needs broader context… losing it w periodic summaries w/o warning caught us off guard the last 2 days.
I’m on v1.4.2 and it’s still completely unusable. It freezes every 10 seconds or so - no memory leaks observed, no CPU or disk spikes, but constant lag. Thought it might be related to indexing, privacy mode, chat history, or extensions, but disabling all of those made no difference. Heck even saving UI state causes a freeze. The last two weeks have been a complete disaster.
Same for me, it’s becoming quite difficult to use. I’m surprised that two consecutive minor releases have had such a noticeable impact in this regard. It would really help if we could access more granular controls to reduce background activity.
I’ll try rolling back to an older version I saved, but I honestly didn’t expect this from a service that’s growing so significantly in importance. It makes me wonder how thoroughly each version is being tested before release.
