[Bug]: "Open in VS Code" Replaces the Current VS Code Window Instead of Opening a New One #34449

Before submitting#

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area#

apps/desktop

Steps to reproduce#

1. Open any folder in VS Code (project A).
2. In T3 Code, open a thread for a different project (project B).
3. In the chat header, click "Open in VS Code".

Expected behavior#

Project B opens in a new VS Code window, and project A's window stays as it was.

Actual behavior#

Project B opens in project A's window and replaces it.

T3 runs code <project path> without --new-window, so VS Code picks the window:

• https://github.com/pingdotgg/t3code/blob/3ed5fb29bd2ffdb31cf146f016300e26ca237f99/packages/contracts/src/editor.ts#L29-L35
• https://github.com/pingdotgg/t3code/blob/3ed5fb29bd2ffdb31cf146f016300e26ca237f99/apps/server/src/process/externalLauncher.ts#L492

Impact#

Major degradation or frequent failure

Version or commit#

v0.1.9

Environment#

Desktop app on Linux Mint

Logs or stack traces#

Screenshots, recordings, or supporting files#

No response

Workaround#

Open a new VS Code window first, or open the folder from VS Code yourself. However, this doesn't always work because t3.code sometimes overwrites the wrong window, which is extremely frustrating.