At least when running Jupyter kernels on remote machines via remote-ssh, kernels will suddenly “freeze” and will not restart. I have to kill the remote VM or SLURM job in order to get the kernel running again. This issue has only started occurring after my update to Cursor 2.3.29.
This is a very disruptive issue for anyone using Jupyter kernels in the Cursor IDE.
This looks like an extensions issue in a Remote SSH environment after updating to 2.3.x. In 2.3 we made changes to extension processes, and that caused a few similar issues with SSH connections.
To help with debugging, can you share:
The Jupyter extension version installed on the remote machine (Cmd + Shift + X, search for Jupyter)
The Remote SSH extension version (should be 1.0.37 or newer)
The remote machine OS (Linux distro and version)
Logs from the Developer Tools Console (Cmd + Shift + I, Console tab) when the kernel freezes
The full list of extensions in the remote environment
Temporary workaround: try reconnecting to the SSH host or restarting Cursor.
I noticed you’re on Remote SSH 0.113.1. Version 1.0.38 was released recently and fixes SSH connection issues after the extension process changes in 2.3.
Can you update Remote SSH to the latest version? In Cursor: Extensions → search for “Anysphere Remote SSH” → Update.
If the kernel hang happens again after updating, please share:
Logs from Developer Tools Console at the moment it hangs
Logs from the “Remote - SSH” tab in the Output panel
Let me know if this helps, or if the kernel hangs again.
Thanks! I didn’t realize that there was a different remote ssh extension. I uninstalled the old extension and installed the Anysphere Remote SSH extension. However, the extension failed to install the server within the timeout:
The kernels are still freezing. I’ll run a cell with other cells in the queue, and the kernel stalls on the first cell, with the Go To button showing activity, but the target cell job has completed and returned output.
I have to restart the kernel and lose all progress, as a result of this issue. The issue is stochastic.
This just opens the agent side panel, so I can’t provide a log.