`code` command launches cursor on Windows 11

[Keita_Kobayashi]

Describe the Bug

code (in addition to cursor) launches Cursor on Windows – both in cmd / powershell, and WSL2, when code should launch VS Code, and cursor should launch Cursor.

Steps to Reproduce

1. Install both Cursor and VS Code on Windows
2. Execute code in the terminal

Expected Behavior

When executing code, I expect VS Code to launch, not Cursor. I haven’t experienced this bug in macOS.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
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.26100

Additional Information

I’m currently working around this by manually patching PATH, but I think that Cursor shouldn’t even ship with a code binary.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[condor]

hi @Keita_Kobayashi and welcome to Cursor Forum

Cursor does not preinstall code or cursor CLI tool, but both options are available and it may ask user on setup if they wish to install those commands.

You can use VSCode to setup the code CLI command back again and then Cursor to setup cursor CLI command .

Documentation and steps:

Cursor – Shell Commands

[CrunchyBuddy]

On Windows I also found that Cursor overrode my code installation with its own. Like the OP the fix was just to swap the VSCode and Cursor entries in my PATH. I recall getting hit by it again in WSL and after a second WTFing I remembered what was going on.

[ravirahman]

Hi @Keita_Kobayashi and @CrunchyBuddy, thanks for reporting this issue. We are looking into it.

[ravirahman]

We expect to have this fixed in the 1.4 release of Cursor.