[FEATURE] Allow "Open in VS Code" to target VS Code Insiders
Problem Statement
The Claude Desktop app's project menu offers "Open in VS Code" alongside "Open in File Explorer" and "New Window." This is hardcoded to launch the stable code build. Users who run VS Code Insiders as their daily driver (for early access to features, extension compatibility testing, or team standardization on Insiders) have no way to make this button open Insiders instead.
Current Workaround
None that don't have side effects - remapping the system code command to point at Insiders would redirect every other tool that shells out to code, not just Claude Desktop.
Proposed Solution
Add an editor preference in Claude Desktop settings (e.g. Settings -> General or Settings -> Tools) letting users choose which VS Code variant "Open in VS Code" launches:
- VS Code (stable) - current default
- VS Code Insiders
- Custom binary path (covers other forks like VSCodium, Cursor, etc.)
Implementation note: VS Code Insiders installs its own code-insiders CLI command and registers a separate vscode-insiders:// URI scheme, distinct from stable's code/vscode://. Whichever mechanism Desktop currently uses to launch VS Code, swapping the target based on a stored preference should be low-risk.
Why This Matters
Editor choice shouldn't require a workaround that affects the rest of the user's system. A per-app setting keeps this self-contained.
Environment
- Claude Desktop
- VS Code Insiders installed alongside stable VS Code
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗