Cursor:// deep links to WSL files no longer reuse the existing Cursor WSL window and now open a new window

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m on Windows + WSL2 (Ubuntu) and use LocatorJS to jump from browser elements to source code via deep links:

cursor://vscode-remote/wsl+Ubuntu${projectPath}${filePath}:${line}:${column}

This previously worked and reused my existing WSL project window.
After troubleshooting and reinstall tests, I can now clearly reproduce a version-specific regression:

Cursor 3.0.16: works correctly (reuses existing WSL window).
Cursor 3.1.15: does not work correctly (opens a new window instead of reusing).
Latest VS Code: works correctly with vscode://… links for the same WSL-targeted workflow.
So this appears to be a Cursor regression in protocol/deep-link handling for WSL remote targets in newer versions, not an issue with my link format.

Steps to Reproduce

Use a Windows machine with WSL2 (Ubuntu), and open a project in Cursor via WSL Remote.
Ensure the cursor:// protocol is registered to Cursor (default installation behavior).
Trigger this deep link (for example from LocatorJS or manually): cursor://vscode-remote/wsl+Ubuntu/home/<user>/<project>/<file>:<line>:<column>
Keep an existing Cursor window for the same WSL project already open.
Click/open the deep link and observe the result.
Actual Result
A new Cursor window is opened instead of reusing the existing WSL project window (in Cursor 3.1.15).

Expected Result
Cursor should reuse the existing WSL project window and navigate to the target file/line/column (same behavior as Cursor 3.0.16).

Version Comparison (for confirmation)
Cursor 3.0.16: works as expected.
Cursor 3.1.15: regression (opens new window).
Latest VS Code (vscode://… with similar WSL workflow): works as expected.

Operating System

Windows 10/11

Version Information

Version: 3.1.15 (user setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. The version comparison and repro steps are really helpful.

This is a confirmed regression. A change that routes Remote-SSH protocol links away from Glass windows ended up being too broad. It catches all vscode-remote:// URIs, including WSL wsl+Ubuntu, not just SSH remotes. That’s why deep links that worked in 3.0.16 now force a new window in 3.1.x.

I’ve flagged this to the team. No timeline yet, but your report helps us prioritize it. As a temporary workaround, you can stay on 3.0.16 if this is critical for your LocatorJS workflow.

I’ll update here if there’s news.

8

Thanks for the reply.

I’m looking for the specific steps to disable auto-updates, as Cursor currently seems to update to the latest version automatically.

Also, once the fix schedule is confirmed, please post an update in this thread so I’ll know when it’s safe to resume updates. Thanks!