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?
Hmm. Lemme think.
Floating composer/composer control panel window, gone…
Review gone and paid for “bugfinder”.
Bugs galore… shorter context.
Long context chat for codebase wide chat with large model, gone…
Agent/Composer feature-set not aligned…
Agent thinks applies fails when diffs fail to load timely (might be because I don’t have GPU capability on what I code on)… and many more if you check complaints for 0.43?
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’ve had a lot of feedback regarding the floating composer, so watch this space…
- The review feature is still available, if you type @ then go to ‘Git’, you can either pick a commit or your PR. The bug finder is a much more comprehensive feature that puts every line of every file in your PR through an LLM. The price we show you is with minimal markup on the raw LLM costs to us, it’s not a feature we price to make money from!
- I’d love some examples of the bugs you have so we can try fix them in our newer releases!
- We haven’t change the context window or what we give the AI between v0.42 and v0.43, so I’d be interested to know what differences you see there
- While we have removed long context mode, we found it’s benefit to be minimal and we think there are much better ways to provide high quality context to an LLM outside of throwing a whole file at it.
- What features are you missing between the two?
- We’ve spotted this too and it should be improved on soon!
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!
Agent/Composer feature-set not aligned…
Assume this is what you’re referring to?
Normal/Agent mode gives different @ capabilities - AKA they’re not at feature parity…
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!
If you want to be really hard core, block download.todesktop.com in your hosts file.
This is of course an awful solution because you’re not only missing any future Cursor updates, but also updates for many other apps.
On the bright side: Since blocking it, Cursor has not once tried to push me to 0.43 and I can use 0.42 in peace and quite.