Connect via SSH: pasting full `ssh user@host -p PORT -i KEY` does nothing (regression); SSH config Host alias still works

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Summary

In the classic Editor window, Connect via SSH no longer accepts a full terminal-style SSH command. Pasting something like:

ssh [email protected] -p 31483 -i ~/.ssh/id_ed25519

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

  1. Open Cursor (classic Editor layout, not Agents-only).

  2. Open Connect via SSH (Command Palette or editor empty state).

  3. Paste: ssh [email protected] -p 31483 -i ~/.ssh/id_ed25519 (use your real host/port/key).

  4. Press Enter or click Connect / a suggested host row.

  5. Observe: nothing happens (no Connecting step, no Output logs).

  6. 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

  1. Connect via SSH → paste full ssh command → Enter → no reaction, no Remote-SSH logs.
  2. 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)

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report, it really helps.

Short answer: the Connect via SSH dialog currently expects either user@host or an alias from ~/.ssh/config. Parsing a full CLI string like ssh user@host -p PORT -i KEY isn’t supported right now, and that’s bad because with that input there’s no error and no logs, the dialog just silently ignores it. It feels broken. I’ve filed an internal report.

Your workaround adding a Host entry in ~/.ssh/config with HostName, Port, and IdentityFile is the recommended approach for now, and it also gives you an alias in the dropdown. Another user reported a similar symptom for non-default ports here: Unable to connect when ssh is running on other ports than 22, same root cause.

I can’t give an ETA for a fix, but at minimum the silent failure with no feedback should be validated and show a clear error. If I get updates, I’ll post them in the thread.