From the latest update, this morning, I’m unable to ‘Connect SSH’ to hosts which ssh server is not running on port 22 (cursor is running on Debian 13).
No errors and no logs.
Steps to Reproduce
Try to connect to an host which ssh server is running on a port different than the default 22
Host .host machine/.host
ProxyCommand /usr/lib/systemd/systemd-ssh-proxy unix/run/ssh-unix-local/socket %p
ProxyUseFdpass yes
CheckHostIP no
Host unix/* vsock/* machine/*
ProxyCommand /usr/lib/systemd/systemd-ssh-proxy %h %p
ProxyUseFdpass yes
CheckHostIP no
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
Host *
StrictHostKeyChecking no
SendEnv LANG LC_* COLORTERM NO_COLOR
HashKnownHosts yes
GSSAPIAuthentication yes
(basically debian 13 stock but ‘StrictHostKeyChecking’ is set to ‘no’)
server side (debian 11):
Port 12345
PermitRootLogin yes
ChallengeResponseAuthentication no
UsePAM yes
X11Forwarding yes
PrintMotd no
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
We released a new version of the SSH extension (anysphere.remote-ssh) yesterday with some stricter validation. We’re going to fix this quickly (might have swung too hard), but in the meantime, you can try reinstalling 1.0.49!
and pressing Enter, or clicking a list item, produces no response at all — the dialog stays on the host step, does not switch to “Connecting”, and Output → Remote-SSH shows no logs.
Connecting via an SSH config Host alias (e.g. gpu-31483 with HostName, Port, IdentityFile in ~/.ssh/config) still works.
Expected behavior
Pasting the full ssh ... command (as I used to do when I switched from VS Code to Cursor) should start the remote connection, or at least show Connecting / errors in the UI or Remote-SSH output.
Actual behavior
Full ssh ... command: no UI change, no Remote-SSH output
Config Host alias: connects normally
Regression
This used to work in Cursor without a dedicated config entry. I only added Host gpu-31483 in ~/.ssh/config as a workaround after the command stopped working. I originally chose Cursor because paste-and-connect with the full SSH command worked for me.
Steps to reproduce
Open Cursor (classic Editor layout, not Agents-only).
Open Connect via SSH (Command Palette or editor empty state).
Paste: ssh [email protected] -p 31483 -i ~/.ssh/id_ed25519 (use your real host/port/key).
Press Enter or click Connect / a suggested host row.
Observe: nothing happens (no Connecting step, no Output logs).
Repeat with only the config alias, e.g. gpu-31483 → connection proceeds.
What I already tried
Developer: Reload Window
Reinstalled Cursor
Reinstalled Remote-SSH extension
Notes
The UI hint says “user@host or select from SSH config”, but the regression is the silent failure when using a full ssh CLI string that previously worked. VS Code documents full ssh commands mainly for Add New SSH Host (writes config); my case is direct connect via Connect via SSH.
Steps to Reproduce
Connect via SSH → paste full ssh command → Enter → no reaction, no Remote-SSH logs.
Same dialog → type config Host alias → Connect → works.
Operating System
MacOS
Version Information
Environment
OS: macOS (darwin 25.x)
Cursor: 3.5.17
Extension: Anysphere Remote - SSH 1.0.51
Remote: Linux (RunPod-style SSH on non-default port)
