Hey, thanks for the report. I reproduced it, and it looks like the cursor-reh server tarball for the latest 3.4.13 build commit e8e1757... didn’t upload correctly to downloads.cursor.com and returns HTTP 403 on all platforms. That’s why Remote-SSH gets stuck on Downloading Cursor Server. Both direct download from the remote and the local fallback fail. AutoDL isn’t the cause here, it’s a general issue affecting everyone on 3.4.13.
This is a release pipeline issue and I’ve escalated it internally. While it’s being fixed:
Workaround: roll back to the previous version 3.3.x
Download the previous stable build from Cursor · Download and reinstall it. It’s currently 3.3.30 on the stable channel.
To stop auto-update from pulling 3.4.13 again until the fix is out, you can temporarily disable auto updates: Settings → Application → Update → Mode = none or manual.
Once the binaries are re-published to the CDN, updating to 3.4.13 will work normally again. I’ll post an update here when I have one.
Hi, thanks for the reply. I managed to upload the cursor server on my own to the server and it seems work. By download the correponding commit server and transimit to autodl server and it seems work. But still I wish to have some better stability that won’t cause any extra trouble. Best.
