Every time I open a folder or open a workspace file, the Anysphere Remote-SSH extension enforces a reconnection (that takes a few seconds to achieve), displaying the usual connection pop-up in the bottom left-hand corner of the Cursor IDE.
Why does the current SSH connection need to be re-connected?
VS Code + Remote-SSH (MSFT version) does not have this issue and is much faster as a result.
Steps to Reproduce
Just use the Remote-SSH extension in Cursor 1.5.11 and try opening a local folder or *.workspace file.
Expected Behavior
Identical behaviour to the MSFT created “Remote-SSH” extension. No need for a SSH connection renegotiation or the time-penalty that results.
Operating System
MacOS
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Hi @mjnowen, we are looking into issues regarding the performance of the remote server, which could cause excessive reconnections.
In the meantime:
Could you check to see if your remote server is running at 100% CPU or memory? If so, could you kill some processes to free up more room for Cursor?
Could you try opening a folder in Cursor that contains fewer files (recursively), or switch to using a multi-root workspace, with just the folders that are needed?
Remote server is <5% CPU and 1.13G/15.3G memory usage. I already use a 10 x multi-root workspace setup. Total of 444 source files in my git repo + .git dir.
My stats don’t feel to me that they should be pushing Cursor that hard. Yet, the re-connects whenever I open the main git repo dir or one of my *.workspace files is considerably slower (in order of a few seconds) compared to VS Code+Remote-SSH user experience. I also don’t see any re-connection/renegotiation taking place in VS Code, compared to Cursor.
I do not think it is the problem of CPU usage. I repeatedly encounter the disconnect/reconnect stall bug on large workspaces. And I second @mjnowen. After a connection fails cursor cannot even SSH connect to small workspaces. Then the only way to connect again is to nuke stale processes and remote cache.
VS code is perfectly fine on workspaces that cursor have trouble ssh into. I think there is something wrong with the remote extension on cursor. Please look into it.