How to make cursor not override the vscode command?

How To
1

Hey, I would love to use Cursor but changing code . to opening Cursor instead of VSCode is such a deal breaker for me.

Is there any setting where I can make sure Cursor don’t override the code command?

I’m on Windows

3 Likes
2

You can reinstall the standard version of VSC and ensure that the “Add to PATH” option is checked during the setup process. This will overwrite the existing code command with the standard VSC.

3

Thanks for the suggestion, but I solved the issue by deleting the code command files from Local App Data > Cursor folder.

I wonder why Cursor add those overriding the code . command though, it’s a bit annoying. They should just stick to cursor .

5 Likes
4

I use Windows and I recently face the same issue. Here is what I did:

  1. Navigate to %localappdata%\Programs\cursor\resources\app\bin (C:\Users\<username>\AppData\Local\Programs\cursor\resources\app\bin for Windows).
  2. Delete two files: code and code.cmd
  3. Make sure that C:\Users\<username>\AppData\Local\Programs\Microsoft VS Code\bin is in the PATH environment variable. (You can edit it by typing Win+R and systempropertiesadvanced)
2 Likes
5

Thanks! This is a very petty move by cursor. You are leeching off VS Code, at least don’t force yourself in its place.

2 Likes
6

This is not the permanent solution, after cursor update it creates those code files in bin again.

7

This is what I did, seems to work: Installing "cursor" shell command overrides "code" as well - #6 by yjmantilla . Or basically:

Problem: Everytime i open cursor it rewrites the files so i need to continuously delete the files.

I converged to instead of deleting the file, just edit the code.cmd from cursor to call the right code.cmd from vscode. E.g:

@echo off
call "Y:\software\Microsoft VS Code\bin\code.cmd" %*

seems to do the trick.