SSH Remote Server Version Mismatch: Client expects non-existent commit hash

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Description:
After updating Cursor today (January 10, 2026), SSH remote connections fail because the client expects a server version that doesn’t exist on the download server.
Environment:
Cursor version: Latest (updated today)
Local OS: Windows
Remote OS: Linux
Issue:
The Cursor client attempts to download the remote server from:
https://downloads.cursor.com/production/4ca9b38c6c97d4243bf0c61e51426667cb964bdc/linux/x64/cursor-reh-linux-x64.tar.gz
However, after extraction, the client looks for the server binary in:
~/.cursor-server/bin/4ca9b38c6c97d4243bf0c61e51426667cb964bd0/
Note the hash difference:
Downloaded: …cb964bdc
Expected: …cb964bd0
The version ending in bd0 does not exist on the download server. Only bdc is available.
Workaround:
Manually rename the extracted folder from …bdc to …bd0:
cd ~/.cursor-server/bin/mv 4ca9b38c6c97d4243bf0c61e51426667cb964bdc 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Root Cause (suspected):
The client binary was released with a hardcoded/embedded version string (…bd0) that doesn’t match the actual server build that was uploaded to the download server (…bdc). This appears to be a release pipeline synchronization issue.
Expected Behavior:
The commit hash in the download URL should match the folder name the client expects.

Steps to Reproduce

Use cursor IDE version 4ca9b38c6c97d4243bf0c61e51426667cb964bd0 it downloads 4ca9b38c6c97d4243bf0c61e51426667cb964bdc server version and causing the issues.

Operating System

Windows 10/11
MacOS
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.29 (user setup)
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

This is clearly a bug in the release pipeline. The client expects a server version that doesn’t match the one being downloaded. I’ll pass this to the team to fix.

For now, your workaround of renaming the folder is the right solution.

2 Likes

Hey @sg777 !

Do you mind giving it another try and let us know if it’s resolved?

Hi @Colin

I tried with workaround by creating the folder under bin with the client commit hash and extracted server zip to it worked.

1 Like