Auto update procedure on Linux, versions 0.45.{8,9,10}

Bug Reports
1

I’m using on Linux. I run it by assigning it a symbolic link called

~/bin/cursor
~/bin/cursor-0.45.8-build-250201b44xw1x2k-x86_64.AppImage

And I start it with

[Desktop Entry]
Name=Cursor
Exec=/home/user/bin/cursor --no-sandbox
Icon=/home/user/bin/cursorIcon.png
Type=Application
Categories=Utility;Development;

Over the past few days (Feb 2-5) I’ve noticed the auto update function behaving aggressively. If I’m not mistaken, the auto update finds the AppImage binary and replaces it with a new image.

Secondly, the reason this came up is because after 0.45.8 auto updated (without me seeing or clicking on the “Update Cursor?” dialog in the bottom left, afaik), version 0.45.9 was buggy and exhibited three odd behaviors:

  1. Total disconnect form Models, this was fixed by a restart

  2. Partial and/or complete disregard for added context. Behavior seemed different depending on @file v. +file.

  3. Hallucinated where to put code and scattered ideas everywhere with slightly different full path.

No big deal, this is complicated stuff and an overall incredible product. I’ll just roll back…

But the auto update overwrote the AppImage. I went to the cursor.sh site and this time it was at 0.45.8 (11a PT) downloaded and made a copy.

Glad I did, same thing happened and i went to the download badge on cursor.sh and found that the 0.45.9 was now the default.

So I use my back up and start watching the change log and this forum. Midday I see the download link was update to 0.45.10 and thanks to a kind poster, I learned that it had some similar bugs so 0.45.8 is probably the best bet. And I had I copy, so all good.

Checking at the end of the day I saw the default download was set back to 0.45.8.

Since I had been personally involved in the ride I know the details. But, that is a lot of change happening in one day about some pretty serious bugs like creating files in hallucinated paths and was surprised not to see any discussion or documentation.

And I’m still curious why 0.45.10 was pushed out to the site and reverted to 0.45.8 today.

Maybe I have missed the patch change log and I could have answered this myself?