[FEATURE] Support configurable config directory in VSCode extension for multi-account setups Problem

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

I use two Claude Code accounts (e.g., Max and Pro) for different projects. In the CLI, I manage this with shell aliases that point to different config directories:

alias claude-work="CLAUDE_CONFIG_DIR=~/.claude-work claude"
alias claude-personal="CLAUDE_CONFIG_DIR=~/.claude-personal claude"

This works perfectly in the terminal. However, the VSCode extension always reads from ~/.claude/ with no way to override it, making it impossible to replicate this workflow in the editor.

Proposed Solution

One or more of the following:

• A VSCode setting (e.g., claude.configDir) that specifies which config directory the extension should use — configurable per VS Code profile or per workspace.
• An environment variable (e.g., CLAUDE_CONFIG_DIR) that the extension respects at launch, so users can set it in a shell wrapper that launches VS Code.
• Built-in account switcher UI in the extension, similar to how VS Code handles multiple GitHub accounts.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_