[FEATURE] VSCode extension 'claudeCode.claudeProcessWrapper' setting should support variable substitution

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

You can set an optional path to claude via the claudeCode.claudeProcessWrapper setting, which is useful for:

• alternate installation locations of claude
• wrapper scripts that authenticate or set up API tokens

However it appears there's no variable substitution available, so things like the following don't work:

• ${workspaceFolder}/claude.sh
• ${userHome}/bin/claude.sh
• ${env:CLAUDE_PATH}/claude.sh

Ultimately the path to the claude wrapper needs to be a hard-coded, absolute path like: /usr/local/bin/claude.sh or /Users/user/projects/ProjectA/claude.sh.

This is a problem because settings may be synced across machines or checked into version control, and the path to claude or the claude wrapper is unlikely to be the same across all machines.

Variable substitution allows the location of the wrapper to be resolved dynamically.

Proposed Solution

I would like to be able to use variable substitution for dynamic resolution of the claude wrapper, such as:

• ${workspaceFolder}/claude.sh
• ${userHome}/bin/claude.sh
• ${env:CLAUDE_PATH}/claude.sh

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

Configuration and settings

Use Case Example

Use case is described above but is generally along the lines of:

1. User A on macOS has claude.sh under /Users/UserA/.local/bin/
2. User B on Ubuntu has claude.sh under /home/UserB/.local/bin/
3. VSCode settings are synced between users & machines, possibly checked into project version control
4. Variable substitution in claudeCode.claudeProcessWrapper allows each each user's claude.sh location to be dynamicaly resolved

Additional Context

_No response_