For the last year i’ve been using cursor and remote tunnels to access compute nodes on a shared SLURM cluster. Today I bought a new MacBook Pro, same cursor major and minor version and Remote Tunnels is not in extensions.
Env - Cursor Remote Tunnel works and is available
Version: 2.6.18
VSCode Version: 1.105.1
Commit: 68fbec5aed9da587d1c6a64172792f505bafa250
Date: 2026-03-10T02:01:17.430Z (5 days ago)
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin x64 25.3.0
Brand new Macbook Pro, cursor 2.16.19, remote-tunnels is not there? Cursor is now unusable in our hpc system and I will need to unsubscribe. This is required for a large SLURM cluster, sshing into a compute node will get you banned.
There are many threads of tunnels but not of them recent. The fact that I two computers in front of me, with cursor, both 2.6.* but one has this critical function and the other does not. Why would remote tunnels disappear from extensions, is there a workaround? SSH is not an option.
Steps to Reproduce
Open cursor 2.6.19 and look in extensions for Remote-tunnel microsoft.
Expected Behavior
Remote tunnels are a critical tool for shared resources.
Hey, this is a known limitation. Remote Tunnels ms-vscode.remote-server isn’t supported in Cursor by default. If it works on your older machine, it’s probably because the extension was cached from an earlier install or import, but it’s not available in the Cursor marketplace.
Recommended workaround:
Use the Anysphere Remote SSH extension anysphere.remote-ssh. It’s built into Cursor.
Since your SLURM cluster doesn’t allow inbound SSH to compute nodes, you can run a forwarding service like Pinggy https://pinggy.io/ or ngrok on the compute node to expose SSH, then connect using our Remote SSH extension.
thank you for your response! I am going to see whether SLURM admin will allow me to expose SSH ngrok-style. For those of you following along (I sense this is important, there are a lot of academics for example that primarily use HPC resources) I will update and confirm whether this workaround is sufficient. For non-HPC users wondering what this is about, sshing into compute nodes on a shared resource side-steps the SLURM system and often triggers an auto-ban.
Cool, let me know how it goes with the SLURM admin. If Pinggy or ngrok don’t get approved, message me and we’ll figure out the next step.
Also, for context, on the old machine the extension probably stayed in the cache after importing from VS Code, so it works there. On a fresh install it’s no longer in the marketplace.
Would it be an extremely hacky solution, to download VSCode, go and get the tunnel extension and place it in the cursor fork? Obviously I’ll go after the more official route, but its not always clear to the user how closely VSCODE and the cursor’s mirror (fork?) of it is and how they diverge. The parallel nature of it makes it tempting to hack things together.
