4.3 is a mess. how do we keep 4.2?
it keeps auto updating with no warning and our workflows go from ‘working’ to ‘useless’
4.3 is a mess. how do we keep 4.2?
it keeps auto updating with no warning and our workflows go from ‘working’ to ‘useless’
Hi,
Currently, the only way to stop Cursor auto-updating is to move it somewhere else on your machine.
On Mac, that means moving the Cursor app out of your /Applications folder.
On Windows, you can copy the whole Cursor install folder elsewhere, and make sure you run the .exe from within the copied folder.
Can I ask, what are the issues you are having with 0.43, that are causing you to downgrade?
So I thought I was crazy and that I was the only one this was happening to, but apparently this newest version of Cursor is failing for a lot of people.
Reverting back to 0.42.5 seems to work for me, but as you may have noticed it will update itself to the broken version again as soon as you use it.
Here is a ghetto temporary solution to maintain your sanity until they fix it…
Download the previous version of Cursor at: https://www.cursor.com/downloads
(for me this was: cursor-0.42.5-build-24111460bf2loz1-x86_64.AppImage)
Write a shell script that you run instead of the binary directly. It deletes cursor, and copies that previous version back in to the binary folder:
#!/bin/bash
echo "Removing Cursor's newest version..."
sudo rm -f cursor.AppImage
echo "Copying over..."
sudo cp /home/matt/Downloads/cursor_042_5.AppImage /home/matt/bin/cursor.AppImage
echo "Setting permissions..."
sudo chmod +x cursor.AppImage
echo "Loading cursor..."
./cursor.AppImage
I know… this is a TRASH solution, however I can’t seem to get cursor to stop itself from auto-updating to the new/incredibly broken version on RHEL9 without stopping other things that are just as important.
To address each of your points:
We’re working to try and find some examples of what is working worse in v0.43 than in v0.42, so if you have any that are clear and obvious, that would be super helpful!
I tried moving mine from apps to documents, on the way it seems to autoupdate back to 43.5…behyond frustrating…also did you manage to download the whole image as I can only seem to get an installer
The Agent composer has tools that it can run to find the files it needs, and to run actions on your files and codebase. As such, some features aren’t needed in Agent mode that are available in the normal Composer.
Is there something specific you think one mode is missing from the other?
All of this seems fine, except can you PLEASE stop force updating!
in the case where a version is broken (like 0.43) you are forcing your entire global set of users to work with a really buggy version.
Couple of bugs: a. It’s constantly scanning my github repo and never finishes b. maybe related, it’s always at 100% cpu.
b makes it unusable.
We should be able to use 0.42.5 until these are fixed and then we can upgrade to a newer version.
–
Gautam
This isnt a trash solution.
It’s literally the only thing that allows me to not lose hours of productivity waiting for Cursor team to fix the issue or worse yet moving to another IDE.
Thank you!
Hey, where do you see that it’s constantly scanning your repo?
If you’re referring to the codebase indexing, it should do every file in your folder once and thats it!
If you have a screenshot, that would be helpful!
I found a way to stop it from updating again after downgrading.
Here’s how to stop Cursor from automatically updating after downgrading to 0.42.5.
After installing 0.42.5, when Cursor is running and you run the
Go to C:\Users\UserName\AppData\Local\cursor-updater on Windows and delete the related files or create a new folder to back them up.
Just in case
C:\Users\UserName\AppData\Local\Programs\cursor\resources
app-update.yml file in C:\Users\UserName\AppData\Local\Programs\cursor\resources and then empty the contents.
I’m not sure, but I think it references this file to generate the update file.
The installer.exe here seems to reference the files in the pending directory to install the files.
Just adding in another anecdote about the massive issues in 4.3, rendering it completely inoperable for me. 4.3 completely breaks chat and composer for me. I get no response and cant include any files in chat. Breaks even simple functionality such as creating new files, auto complete, indexing, etc. It keeps auto updating at which point I have to remove cursor and reinstall an old version. This fix works until i restart my PC, at which point it will update to the broken version. I am using Ubuntu if that provides any insight. Would be nice to include a built in option to switch to a different version or even turn off auto update.
Hi @danperks, thanks for the prompt response.
So I don’t think that is the underlying issue in my case. I ran the command and did in fact already have GLIBCXX version 3.4.20, in addition to newer and older versions.
Why is cursor so hell bent on releasing buggy software that is a net negative? Cursor too new to play microsoft.
Cursor could be the new movable type. Sorry, what’s that? “you don’t know what movable type is”, they were bigger than wordpress, because they didn’t keep up they got left behind. “Oh” so you are saying they are like myspace, which was bigger than facebook.
Ahhh, yes cursor you will be damned to history if you keep this up. People are already trying to backpeddle away from new updates- what is this telling you? You are a new company, around for what a couple months? people are already demanding refunds, you are buying up companies (supermaven) then killing them? I admire the arrogance, but you gotta be huge to play that game- the only game in town. apple plays this, microsoft, FB and a few others- 60 milly does not make you huge.
listen to the customer.
Working, thanks!
Linux download. For MacOS, there is only the installer downloaded (a few 100 kb).
Linux is .AppImage, Mac is just a small installer zip.
on mac go to applications > cursor icon > show Package content > Contents > Resources > open app-update.yaml delete everything in it
Hey,
To be clear, the PR review feature is still available and is included in your subscription. All that has changed is where you can find the feature (under the @ menu).
The bug finder feature is experimental but is a very different way of triggering a review. It’s a specifically new feature but, due to the cost of raw LLM usage the feature uses, we cant price it into the Pro plan.
sorry for the delayed response… attaching a screen shot.
It scans, never stops, goes to 100% CPU and that is (waited 10 minutes).
No issues in 0.42.5.
Sounds like you guys aren’t doing enough regression testing across OSes and platforms…?
This would be barely acceptable in a free opensource product. With a paid product, this is completely unacceptable.
Still love Cursor and have enjoyed it thus far. Not too late to fix the process and importantly the bugs.
Please don’t make us abandon the project and go back to gasp VSCode or other…