Please stop overwriting the `code` CLI – it's causing workflow issues

I know this topic has already come up in previous discussions on the forum — I’ve read those threads — but as of now, this behavior still hasn’t changed, so I want to raise it again.

Every time Cursor updates, it overwrites the code command on my system. This has become a recurring issue for me.

I use both VS Code and Cursor side by side. In some workflows, I still need to use the official VS Code, and it’s important for me that the code command continues to open it reliably.

While I can manually restore the code symlink back to VS Code, Cursor updates consistently revert this change without notice, which interrupts my setup.

It would be great if Cursor could:

  • Avoid overwriting the code command by default
  • Or provide a configuration option to disable this behavior

I really enjoy using Cursor and want to keep it alongside VS Code, but this recurring issue makes that difficult.

1 Like