Cursor CLI version mismatch 1) breaks remote tunnels and 2) can't be updated

Cursor CLI version mismatch 1) breaks remote tunnels and 2) can’t be updated

Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:

:white_check_mark: Check the forum to ensure the issue hasn’t been reported already
:lady_beetle: Provide a clear description of the bug
:counterclockwise_arrows_button: Explain how to reproduce the bug (if known)
:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
:laptop: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
:prohibited: Tell us if the issue stops you from using Cursor.

:lady_beetle: My cursor-tunnel has stopped working: it’ll just hang on “Opening Remote” / “Connecting to dev-gpu” and then time out with “Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)”. This started happening on Friday and O3 and I haven’t been able to figure it out yet.

rm -rf ~/.cursor* doesn’t fix it.

My leading theory is a version mismatch:

  • My laptop’s cursor --version is 0.50.7 (the latest available).
  • The CLI on worker nodes /mnt/polished-lake/scripts/code-servers/cursor --version is at 0.45.14.

However, it’s been surprisingly tough to bring them in line:

  • Trying to upgrade the CLI with /mnt/polished-lake/scripts/code-servers/cursor update incorrectly prints that it’s already up-to-date. (Cursor bug?)
  • Downgrading my local Cursor to 0.48 (the oldest available on Downloads | Cursor - The AI Code Editor) doesn’t fix it. Reinstalling a new tunnel at 0.48 does it, but Cursor auto-updates itself on restart, re-breaking the tunnel.
  • We found the CLI via a link we found in a forum post here: https://api2.cursor.sh/updates/download-latest?os=cli-alpine-x64. However, this still installs 0.45.
  • It’s not easy/obvious for how to install a CLI manually (surely I’m missing something here?). So I downloaded the Linux x64 .AppImage manually, SCP’d it to the Kubernetes control plane, unpacked the .AppImage with ./cursor.v50.AppImage --appimage-extract, then dug into the resulting app directory and tried executing each of the 8 cursor files inside of the app directory but none of them are the CLI.

:laptop: Locally, I’m on Mac Sequoia 15.1. My Kube control plane and worker nodes are Linux x86_64 machines running Ubuntu 22.04.5 LTS.
:prohibited: Yes, this prevents me from using Cursor.

1 Like

Hi! We do not provide an official Cursor cli for tunneling. We would instead recommend to use a reverse ssh tool, such as ngrok, to expose access to your remote system, and then use the remote ssh plugin to connect.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.