claude-code - 💡(How to fix) Fix [FEATURE] Ability to customize the launch command for Claude Code for VS Code [1 participants]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

I use a custom alias (ccr code) for launching Claude Code in my workflow to better manage multiple environments and configurations. Currently, the VS Code extension hardcodes the launch command to claude, which means I cannot use my custom alias or alternative commands to start Claude Code from within the editor. This forces me to launch Claude Code manually from the terminal every time I want to use my preferred command, breaking my integrated workflow and preventing me from using the extension’s built-in launch functionality with my setup. I need the extension to support a configurable launch command so I can use aliases like ccr code instead of being limited to the hardcoded claude command.

Proposed Solution

I’d like the VS Code extension to support a customizable launch command that users can configure via VS Code settings, replacing the current hardcoded claude command. The ideal workflow would work like this: In VS Code Settings, I could search for a new option like Claude Code: Launch Command I’d enter my preferred command, such as ccr code (or any other alias/custom launch command) When I use the extension’s built-in "Launch Claude Code" action, it would run my configured command instead of the hardcoded claude The extension would automatically pass the current workspace path as an argument to my custom command, just like it does with the default command If no custom command is set, it would fall back to the default claude command to maintain backward compatibility This would let me use my custom alias directly from within VS Code, without having to switch to the terminal every time.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

Configuration and settings

Use Case Example

No response

Additional Context

No response