1. persistent disconnect loop 2. connection failed on saved projects

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

  1. As is common with vs-code persistent disconnect / reconnect loops freeze remote server. I had solved this issue months ago but it returned after most recent update so I went through usual ServerAliveInterval settings etc. to no avail.

  2. “Connection to Cursor server failed: Failed to connect to the remote SSH host. Please check the logs for more details.” - after recent update all saved projects can no longer be connected, so a new connection has to made but this in turn removes agent history from the IDE view, but, the agents window still contains the agent chat history but can not be engaged with from that point either as the agent window attempts its own connection which also fails.

please advise

Steps to Reproduce

  1. open a project that existed before recent updates

Expected Behavior

unbroken connection to remote server - saved projects should re-connect on open with full agent chat history - agents window should also connect to remote and act upon commands using existing history.

Operating System

MacOS

Version Information

Version: 3.5.33
VSCode Version: 1.105.1
Commit: aac81804b986d739acab348ed96b8bea6e83cc50
Date: 2026-05-22T06:47:48.039Z (5 days ago)
Layout: editor
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: Darwin arm64 22.1.0

For AI issues: which model did you use?

composer 2.5

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Both of these are known issues tied to a recent update of the Remote SSH extension.

Saved projects failing to connect: The extension update that shipped on May 22 introduced a regression that can break reconnection to previously saved projects. Our team is aware and working on a fix. In the meantime, you can work around this by defining your SSH hosts in ~/.ssh/config (if you haven’t already) and connecting through the config alias rather than the direct user@host format.

Agent history: Your chat history isn’t lost. It’s still stored on disk, just inaccessible when connecting through a different workspace path. Once the fix ships and you can reconnect to your original saved projects, it should reappear.

Disconnect loop: If the reconnect cycle persists, try killing the multiplex-server process on the remote (pkill -f multiplex-server) and doing a Reload Window (Cmd+Shift+P > “Developer: Reload Window”) in Cursor. Our team is actively working on improving SSH reconnection stability.

You may also find this related thread helpful: Bug Report: Remote SSH extension v1.0.51 breaks Connect to Host