[FEATURE] Allow the new Claude VS Code extension to configure the claude executable path

Resolved 💬 4 comments Opened Sep 30, 2025 by justin39 Closed Oct 21, 2025

Preflight Checklist

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

Problem Statement

The new Claude VS Code extension seems to always spawn claude from the bundled claude-code package:

node /home/user/.vscode-server/extensions/anthropic.claude-code-2.0.0/resources/claude-code/cli.js --output-format stream-json --verbose --input-format stream-json --append-system-prompt [...]

This may be because the extension is unable to find a native installation or a global NPM install of claude-code - instead, we use a wrapper script on PATH. This wrapper script performs some convenient setup, like setting up some infrastructure and the environment variables required to run Claude with our third-party model provider. The bundled claude-code doesn't perform this bootstrapping and won't work.

Proposed Solution

I would like to be able to configure the extension to use a claude executable by path.

Alternative Solutions

It's possible to rig up the environment variables via claude-code.environmentVariables settings in VS Code, but this is manual and doesn't fully cover the setup required.

Priority

High - Significant impact on productivity

Feature Category

Developer tools/SDK

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗