Connection Error using SSH

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

If I am using the same Cursor client without SSH for local project, agent chat works fine.
But if I am opening a remote project via SSH, agent chat shows Connection Error with Request ID: e00d2453-fbff-43af-9adc-bc72e31e77be

Steps to Reproduce

using SSH to connect to remote project and send anything in agent chat.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.32 (user setup)
VSCode Version: 1.105.1
Commit: ef979b1b43d85eee2a274c25fd62d5502006e420
Date: 2025-11-25T05:00:12.749Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report. Agent connection errors over SSH are a known issue we’re already tracking.

Please try the following steps:

  1. Start a new chat:
    Sometimes the error gets stuck in a specific session, and starting a new Agent session can clear it.

  2. Run Network Diagnostics:

    • Settings → Network → Run Diagnostic
    • Share the full output here

  3. Check SSH connection logs and console errors:

    • Help → Toggle Developer Tools
    • Share any errors or warnings you see there
    • Open the “Output” panel: View → Output
    • In the dropdown, select “Remote-SSH”

  4. Check MCP servers:
    If you have any MCP servers configured in Tools & MCP, temporarily disable them.

It would also be helpful if you could clarify:

  1. Are you connecting via SSH to a Windows host or a Linux host?
  2. Are you using any firewall or antivirus software?
4

Thanks for reply!

  1. new chat won’t help. Connection error still shows.

  2. Network Diagnostic seems fine, only Ping response took longer but it’s not blocking chat when I use chat without SSH.

  3. error in developer console:

    DeveloperTools.txt (3.8 KB)
    RemoteSSH in output view doesn’t show error, setup is OK with server listening.

  4. No MCP servers setup.

    I’m connecting SSH to from Windows to Windows. Firewall is Windows Firewall but 1 week ago it works fine.

6

Just now, with another hit in new chat, it runs through now… Monitoring if it is consistent.

8

unfortunately, very unstable, not working again.

10

Inspired by other user’s post, I found the issue can ONLY be gone when Output panel with “Remote-SSH“ selected. Other panel in display like “Terminal“ or “Debug Console“ instead of “Remote-SSH“ of Output will block chat agent. @deanrie

2 Likes
12

same here. new chat also gives same error.

15

same here. just like @Thomas_Li said, with “Remote-SSH“ selected in the “Output“ panel, the agent will work.