Cursor hijacked vscode in my WSL

Bug Reports
1

Describe the Bug

After installing Cursor and using it on WSL, the command “code .” opens Cursor and not Code. Reinstalling vscode did not fix it. I now have no code support for my projects in WSL.

Steps to Reproduce

Not sure. I have yet to try uninstalling Cursor.

Expected Behavior

I would expect typing “code .” would start vscode in the current directory.

Screenshots / Screen Recordings

Cursor.png
Cursor.png3435×1437 207 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.3 (user setup)
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

3

Hi @Dexter_Le_Blanc

You can fix this by changing the command in Cursor to be ‘cursor’ instead of ‘code’ and then going to vscode and setting up the same command to be ‘code’

Shell Command: install ‘code’ command

‘code’ for vcscode and ‘cursor’ for for cursor

image

PS> welcome to the forum :slight_smile: