Remote-SSH crashes if server path contains space

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Problem Statement

cursor-server does not start correctly when invoked remotely (via Anysphere Remote-SSH extension) on Windows, when the remote username or server install path contains a space.

Root Cause

I’m aware that spaces in paths are not good practice, but my username is set by my IT department in the format Firstname Lastname, so the default directory for Remote-SSH to use on the remote host is C:\Users\Firstname Lastname\.cursor-server. The particular argument which causes issues is --connection-token-file $SERVER_TOKENFILE as SERVER_TOKENFILE is passed without quotes, so the server effectively sees an argument of --connection-token-file C:\Users\Firstname and is not able to open that non-existent file.

How to Fix on Cursor’s Side

Escape spaces in paths or quote the paths passed to the server binary.

User Workaround

Use the Remote-SSH settings to set a different server install path which does not have spaces in the path.

Other Complaints :slight_smile:

Not strictly related to this bug, but this was devilishly hard to track down because Remote-SSH did not provide useful logs. It checked that the server started, and then complained that the logfile didn’t exist (it was looking for the logfile to determine the port to connect to: Checking for server port from log file C:\Users\Firstname Lastname\.cursor-server\.655ee705c6c7b6da1da481d0fdf13191d5e3e980.log followed by Error server log file not found C:\Users\Firstname Lastname\.cursor-server\.655ee705c6c7b6da1da481d0fdf13191d5e3e980.log). There was never a hint that the server had actually crashed, I spent a lot of time chasing down why the server was failing to redirect its output to the logfile, and for whatever reason the log line that mentioned issues opening the token file wasn’t redirected to the logfile itself.

Steps to Reproduce

  1. Set Remote-SSH “Server Install Path” setting (remote.SSH.serverInstallPath) to a path containing a space
  2. Attempt to connect to the remote Windows host

Expected Behavior

cursor-server should not exit unexpectedly

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.23
VSCode Version: 1.105.1
Commit: 655ee705c6c7b6da1da481d0fdf13191d5e3e980
Date: 2026-01-06T04:26:58.029Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report.

I’ve passed it to the team to fix. The issue is that arguments with spaces aren’t being escaped when launching cursor-server, and it looks similar to a few other known issues we have with path handling.

For now, use the workaround you found and set remote.SSH.serverInstallPath to a path without spaces.

1 Like
4

Hey @dddredfern I am Tarun!

The fix is up for this issue in our next version 1.0.37, look out for the update (sometime today)

Thanks for reporting Derek, appreciate it!!

1 Like
6

We released version 1.0.37 of the extension; can you try upgrading to that version which incorporates the fix?

2 Likes
7

Confirmed, it works! Thanks for the quick fix!

1 Like