Cursor isn’t generally “slow,” but shows periodic stuttering: approximately every 30 seconds, remote operations freeze for about 5 seconds. During each freeze:
File open/save and explorer operations hang.
Integrated terminal input/echo pauses, then resumes.
The UI remains otherwise responsive.
This occurs only when connecting from A to C via B (C’s SSH exposed on B using frpc or SSH forwarding). The same connection path in VSCode is smooth, and Cursor connecting directly to B is fine. Reproducible with client A on both macOS and Windows 10/11. Bastion B and target C both run Ubuntu 22.04. This issue has persisted for roughly three months; Cursor has been kept on the latest version throughout with no fix so far.
Steps to Reproduce
On B, expose C’s SSH (C:22) via frpc or an SSH forward so that B:PORT forwards to C:22.
On A, in Cursor, create a Remote-SSH target to B:PORT (which reaches C’s sshd).
Connect and open a folder on C.
Perform typical actions (open/save files; run git status, ls -l, or tail -f in the terminal).
Observe a repeating pattern: roughly every 30 seconds, all remote file ops and terminal I/O freeze for ~5 seconds, then continue.
Expected Behavior
No periodic stalls; file operations and terminal I/O remain continuously responsive.
Performance comparable to VSCode on the same connection path.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
I’ve been experiencing similar stuttering issues since version 1.4. Interestingly, this happens even with a regular remote SSH connection (not just the two-hop setup you mentioned).
Also noticed the problem is node-specific as one node connects fine for me while another node regularly freezes.
The same issue has appeared since version 1.4. Do you have any thoughts on the differences between your nodes? Maybe that could help solve the problem.
I wrote this bug report and now I found yours, which is very similar. I agree with “A to C via B” connection is the problem. Only difference is the period (for me it’s 60sec)
I turned off indexing and used a relay server to connect through two simultaneous jump paths—A → B → C and A → D → C—using two IDE terminals within the same tmux session. During testing, even with an empty project open, the lag persisted and occurred at the same time on both paths. It’s clearly not a network issue, since vscode and pure terminal were running smoothly at the same time.
Thank you for your reply. I tried, but it didn’t change the situation. The problem isn’t just with the terminal — the lag also happens when opening and saving code files.
It happens on my end with A → B direct connection. This is very frustrating as it freezes frequently. The whole terminal freezes and I’m able to open or save any files @ravirahman
