Ipynb kernel selection doesn't work on remote after update 2.3->2.4

[splitkeyboard]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I usually “connect remote” → “ssh to host” from my macos cursor to my windows pc on the local network. I have .venv setup on windows which I use as a kernel to run my .ipynb notebooks.

Since last update, the “Select Kernel” → pick .venv from the list, stopped working.
The button stays at “Select Kernel”, there are no logs reporting any issues and I’m unable to run my .ipynb on remote.

for context, .venv for kernel works fine locally on both macos and windows, the bug concerns remote only.

I tried dumping .cursor-server, reinstalling extensions, reinstalling server etc. Nothing seems to help.

Steps to Reproduce

1. ssh remote from macos cursor to windows 10 on local network
2. open folder with .venv and .ipynb (I used uv, if that helps)
3. press “Select Kernel” in upper right corner.
4. choose python .venv from the list
5. nothing happens

Expected Behavior

I expect the “Select Kernel” to recognize the remote .venv correctly which would allow me to run .ipynb notebooks on remote, as it worked before.

Operating System

Windows 10/11

Version Information

Version: 2.4.22
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.4.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[splitkeyboard]

had to roll back to cursor 2.3 where everything works as expected

which proves the point something slipped in 2.4?

for context, works fine on 2.3
Version: 2.3.35
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.4.0

[deanrie]

Hey, thanks for the report. This looks like a regression in 2.4 for Jupyter over SSH.

Try a few things:

• Check the Anysphere Remote SSH version: in Extensions it should be 1.0.38 or newer. If it’s older, update it.
• Disable Cursor Tab: there was a thread where Jupyter over SSH stopped working in 2.4 because of Tab completions. Go to Settings > Tab > Cursor Tab and set it to disabled. Restart Cursor, then try connecting over SSH again.
• Jupyter extension version: what version do you have on the remote machine? (CMD+Shift+X, then search “Jupyter”)

If none of that helps, you can stay on 2.3.35 for now until we fix the regression. Let me know what you find, especially about Cursor Tab. If that’s the cause, it’s useful info.

[splitkeyboard]

Hi!

1. indeed it’s at 1.0.38

• I found this in the Runtime Status of the extension, fyi

Runtime Status
Activation
Activated by onResolveRemoteAuthority:ssh-remote event: 2ms
Uncaught Errors (1)
Windows SSH hosts are not supported for intermediate resolvers (1)

2. Disabling tab didn’t fix the issue
3. Version 2025.4.1

> ps

I did notice this error in my runtime for Jupyter Extension though, cursor 2.4

”/c:/Users/user/.cursor-server/data/User/globalStorage/ms-toolsai.jupyter/version-2025.4.1/jupyter/kernels contains invalid WIN32 path characters.”

I tried mitigating this by adding the correct path to jupyter.kernels.trusted.

• didn’t work

I also recalled seeing the configuration prompt when sshing into remote for the first time (cursor asks to choose the remote OS), so I tried reconnecting to remote and chose windows.

• didn’t help

I will stay on 2.3.35 for now, I hope the info above can help you in some way!

thanks a lot for your help!