CODE and CURSOR command creation overriding VSC
Your suggested feature of creating either the code command OR the cursor command will entirely override the VSC command code from the path DESPITE only having selected the cursor command!
Furthermore your uninstalling option of the command DID NOT UNINSTALL the cursor command even after restarting the system.
I'm on Windows 11 but the same happened on 10 a few weeks back.
Same problem: $ code .bashrc Unable to determine app path from symlink : /c/Users/me/AppData/Local/Programs/cursor/resources/app/bin/code
This is because Cursor is just naively adding the /bin dir to the System PATH:
C:\Users\lesmo\AppData\Local\Programs\cursor\resources\app\bin
This folder contains cursor and code binaries, which are overriding VS Code. This is wrong, Cursor should be adding itself to the User PATH, not System PATH (Cursor devs please take note).
To fix this, the VS Code path must be set before Cursor. I recommend removing Cursor from the System PATH, and adding it at the end of the User PATH. If you want to replace Code with Cursor, just remove Code from the PATH.
Same problem: $ code .bashrc Unable to determine app path from symlink : /c/Users/me/AppData/Local/Programs/cursor/resources/app/bin/code
This is a different problem and probably should have its own issue.
Cursor is shipping with the same CLI script it uses for *NIX, which is not prepared to work with WSL. I couldn't find a workaround, so right now you'll need to go through Cursor, switch to WSL and then open your folder.
I couldn't find a workaround, so right now you'll need to go through Cursor, switch to WSL and then open your folder.
I managed to figure out a functional workaround. You can find it here.
I'm surprised the issue hasn't been resolved yet.
This is extremely frustrating and pretty unacceptable, installing Cursor just to try it out completely breaks VS Code opening from WSL requiring completing uninstalling and reinstalling VS Code.
Overriding another app's functionality is completely unacceptable.
It is unfortunate because this completely prevents using this on anything but personal projects and makes it impossible to recommend to any serious company.
This is because Cursor is just naively adding the
/bindir to the System PATH:C:\Users\lesmo\AppData\Local\Programs\cursor\resources\app\binThis folder contains
cursorandcodebinaries, which are overriding VS Code. This is wrong, Cursor should be adding itself to the User PATH, not System PATH (Cursor devs please take note).To fix this, the VS Code path must be set before Cursor. I recommend removing Cursor from the System PATH, and adding it at the end of the User PATH. If you want to replace Code with Cursor, just remove Code from the PATH.
Thank you so much man! That worked 100%
I just removed the code and code.cmd files from the bin folder /mnt/c/Users/Michael/AppData/Local/Programs/cursor/resources/app/bin/code the command code is pointing to VSCode again.
I just uninstalled Cursor because of this lol. You can do pretty much anything but fuck up my command line and you're done. As for the linked issue: Calling this "some edge cases" is wild.
Same issue here. Had to remove files from the bin folder. This should not be happening. Installing cursor should by no means be messing up with the command line and altering commands without explicit user confirmation.
I just removed the code and code.cmd files from the bin folder
/mnt/c/Users/Michael/AppData/Local/Programs/cursor/resources/app/bin/codethe commandcodeis pointing to VSCode again.
I did this a few days ago, and life was good, but today all of the sudden they decided to create themselves again. I am going to try the solution @lesmo provided above (so thank you 🙏), but I should not have to edit the PATH to get functionality out of both Vsc and cursor from the command line. A bit ridiculous that this has been an open issue for over a year at this point.
Same problem here. Fix it, guys.😊
Your product is for developers and messing up with their setup is unacceptable. Had to uninstall as well
Is this still a thing? Infuriating.
Simple rule - no software should remove or incapacitate any other software for any reason with users explicit permission. This is why Cursor is banned at several of my high profile customers. Too many support calls.
