SSH Remote: Slow connection due to checking all cursor-server versions in shared environment

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When connecting to a shared Linux server (multiple users share the same account), the SSH connection takes 1-2 minutes because the installation script iterates through ALL cursor-server versions in ~/.cursor-server/bin/.

In our case, we have 16 versions accumulated over 3 months, and each version check takes ~5-6 seconds.

Logs:

2025-12-10 16:06:59.691 [info] Started installation script. Waiting for it to finish...
2025-12-10 16:07:02.009 [info] Server script already installed

# Issue: iterating through all versions (~5-6 seconds each)
2025-12-10 16:07:08.091 [info] Build 9cd7c8b6... is still running, skipping
2025-12-10 16:07:13.720 [info] Build multiplex-server is still running, skipping
2025-12-10 16:07:19.637 [info] Build ef979b1b... is still running, skipping
2025-12-10 16:07:25.194 [info] Build ba90f2f8... is still running, skipping
2025-12-10 16:07:30.654 [info] Build 63fcac10... is still running, skipping
2025-12-10 16:07:36.561 [info] Build 8e4da76a... is still running, skipping
2025-12-10 16:07:42.626 [info] Build 54c27320... is still running, skipping
2025-12-10 16:07:48.848 [info] Build 5c17eb29... is still running, skipping
2025-12-10 16:07:54.582 [info] Build b9e5948c... is still running, skipping
2025-12-10 16:08:00.215 [info] Build a9c77cea... is still running, skipping
2025-12-10 16:08:05.948 [info] Build af58d926... is still running, skipping
# Total: ~60 seconds just for version checking

2025-12-10 16:08:17.737 [info] Server install command exit code: 0

Steps to Reproduce

  1. Set up a shared Linux server where multiple users share the same account (e.g., root)
  2. Each user uses different versions of Cursor client
  3. Over time, multiple cursor-server versions accumulate in ~/.cursor-server/bin/
  4. Connect via SSH Remote - observe the slow connection time

Expected Behavior

The installation script should only check the target version needed by the current Cursor client, not iterate through all versions in the bin directory. This would reduce connection time from 1-2 minutes to just a few seconds.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 22.6.0

Additional Information

  • Environment: Shared Linux server, multiple users with different Cursor client versions
  • Number of cursor-server versions: 16 (accumulated from Sep to Dec 2024)
  • Total disk usage: 3.3 GB for cursor-server versions
  • Each version check takes ~5-6 seconds due to SSH command round-trip

Suggested fix: Optimize the installation script to directly check the required version hash instead of iterating through all directories in ~/.cursor-server/bin/

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

This is part of a clean up operation. It’s possible that dangling servers are being left behind. If you’re sure no one is connected, feel free to manually remove these folders and kill the processes – they’ll be redownloaded / reinstalled if needed.