[axpvms]

maybe they changed some things last I used it, which was maybe six months ago. I've tried cursor twice and had the same issue each time. I saw the dialogue you were talking about and specifically selected to not override the code extension and it happened again anyway. Maybe there was something left over from the previous install, I don't know.

I was using windows and wsl, and they were adding scripts to my profile directory (code.cmd) which then took precedence over vscode, from what I remember. Tracking that down required googling to discover other people who were having the same issue. If this is what I have to do when I first start using a product, it just leaves a bad impression. Additionally it seems that it will hijack the 'code' alias in WSL if you select this option or not, which is where I primarily use it. And then when cursor updates, it seems it will again attempt to overwrite this alias.

I'm not the only one who encounters this issue https://github.com/getcursor/cursor/issues/2654 https://github.com/getcursor/cursor/issues/2566 https://forum.cursor.com/t/do-not-hijack-code-shortcut/60671 https://namvu.net/2025/01/cursor-stole-your-code-command-her...

Maybe it works great for other people and they never encounter this issue. Maybe it seems like a petty thing. For me it seems it's implemented to attempt to 'force convert' some vscode users to use cursor all the time, and maybe that works and it's a success from a business perspective. But I won't use it again.

[doix]

Ouch, that does sound painful. I've only ever used it on Linux and Mac which work similar enough that if it did override it, it would be a mild annoyance at best.

I don't know windows + wsl enough that I'm sure I would've been caught out by that and pissed off as well.