SSH connection cannot be open

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

I am trying to connect to a SSH connection (which is something i did in the past), but after migrating to a new PC this action can’t be done.
Please need your help it is very urgent and affective my work.

Steps to Reproduce

open cursor → ctrl + shift + p → ‘connect via SSH’ → config file <which I already created and use in the past and it worked) → password → select the relevant folder →

now after click ‘open’ it is loading for 2 seconds and then the wizard is gone and nothing happen.

Expected Behavior

The expected behaviour is that the SSH connection will be open.

Operating System

Windows 10/11

Version Information

Version: 3.3.30 (user setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

This is a known bug with the current layout. After selecting a folder and clicking Open, the workspace silently fails to load.

Workaround: Try switching to the editor layout. Open Command Palette (Ctrl+Shift+P) and search for “Toggle Glass” or “Layout” to switch. SSH connections should work in the editor layout. You can switch back once we ship a fix.

Our team is actively working on resolving this. If switching layouts doesn’t help, could you open Help > Toggle Developer Tools > Console tab right after the connection attempt fails, and share any error messages? That would help us confirm the exact issue on your end.

Hey @Roni_Dabah,
The SSH connection issue has been addressed in a recent Cursor update. Updating to the latest version should resolve this — let me know if you’re still running into it!

Thank you!

I’m seeing this exact behavior on:
Version: 3.12.17
VS Code Extension API: 1.128.0
Commit: 0fb762053c34788bb7760d5673f8a6d4c8589d50
Date: 2026-07-17T02:53:53.006Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Linux x64 7.0.0-28-generic

Hey @C_ST,The bug this thread tracked was a Glass SSH connect flow that closed without opening the workspace, and that was fixed back in the 3.6 line. Since you’re on 3.12.17, that fix is already in your build, so what you’re hitting on Linux + Agents Window is a separate occurrence rather than the same bug. It’ll get lost if it rides along on a resolved thread, so it’s best tracked on its own.

If you need to unblock quickly in the meantime: opening the SSH workspace from the classic Editor Window (instead of the Agents Window) has worked around this for others while the Agents Window flow is sorted out.

When you get a chance, could you open a new bug report in the Bug Reports category with:

  1. OS, Cursor version, and layout (Linux, 3.12.17, Agents Window) — you’ve already got these
  2. The exact step it fails at (e.g. after selecting the folder and clicking Open), and whether opening the same host from the classic Editor Window works
  3. Dev Tools console output right after the failed attempt: Help → Toggle Developer Tools → Console tab, then screenshot or copy any errors
  4. Logs: Ctrl+Shift+P → Developer: Open Logs Folder, and share the Remote - SSH and Extension Host logs from around the connection attempt
  5. Whether this is a new host or one that connected fine before

Thakns Mohit - here is the new link: SSH in Agent Window Disappears