Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
This existing thread was closed, but I’m hoping to push on this a bit more since this bug still exists on version 3.2.21. This is very annoying for enterprise employees who use remote dev environments.
Can we get an update on this fix and leave this thread open or reopen the existing thread until there is a fix?
cc @untaku
Steps to Reproduce
Quote from original thread:
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///::
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 Behavior
Cursor should reuse the existing WSL project window and navigate to the target file/line/column (same behavior as Cursor 3.0.16).
Operating System
MacOS
Version Information
Version: 3.2.21 (Universal)
VSCode Version: 1.105.1
Commit: 806df57ed3b6f1ee0175140d38039a38574ec720
Date: 2026-05-03T01:46:14.413Z
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: Darwin arm64 25.4.0
Does this stop you from using Cursor
No - Cursor works, but with this issue