[BUG] Claude Code extension installs only in VSCode "Default" user profile

[ZetabS]

Environment

• Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other:
• Claude CLI version: 1.0.11 (Claude Code)
• Operating System: Linux Mint 22.1 (xia)
• Terminal: VSCode Integrated Terminal (Bash)
• VSCode: Visual Studio Code 1.100.3

Bug Description

Claude Code extension installs only in the "Default" user profile in VS Code (not terminal profiles).

When running claude in the integrated terminal:

• The extension installs correctly when the active VS Code profile is "Default".
• If all profiles are reset and a non-default VS Code profile (e.g., "Javascript") is active,
  running claude installs the extension only in the "Default" profile, not the currently active profile.

This breaks expected behavior in projects that rely on customized profiles (e.g. language-specific configurations).

Steps to Reproduce

1. Open VS Code and ensure you have multiple VS Code user profiles (e.g., "Default", "Javascript").
2. Remove the Claude extension from all profiles.
3. Activate the "Javascript" profile (or any custom profile).
4. Run claude in the integrated terminal.

Expected Behavior

Claude Code should install and activate only in the currently active VS Code profile (e.g., it should be installed in "Javascript", not in "Default"). It should not install into the "Default" profile unless "Default" is the currently active one. Installing extensions into inactive profiles breaks the conceptual isolation that VS Code profiles are designed to provide, and may lead to unexpected behaviors or misconfigurations.

Actual Behavior

Claude Code installs in the "Default" VS Code profile regardless of which profile is active.

Additional Context

• This bug is unrelated to "terminal profiles" — it concerns VS Code's user profiles, as described in the official documentation.
• The documentation states:

  "VS Code treats your current configuration as the Default Profile. As you modify settings, install extensions, or change UI layout... these are tracked in your active profile."

• I installed Claude CLI using: pnpm add -g @anthropic-ai/claude-code This placed the .vsix at:
  ~/.local/share/pnpm/global/5/node_modules/@anthropic-ai/claude-code/vendor/claude-code.vsix

Workaround

To manually install Claude Code into the correct VS Code user profile:

code --profile "Javascript" --install-extension ~/.local/share/pnpm/global/5/node_modules/@anthropic-ai/claude-code/vendor/claude-code.vsix

This successfully installs the extension in the "Javascript" profile.
However, this workaround is not obvious from the documentation and requires users to locate the VSIX path manually.

[jest]

Regarding "Expected Behavior" above:

Claude Code should install and activate in the currently active VS Code profile, not just the "Default".

to clairfy, I think that Claude Code should install the extension only in the currently active profile, not touching the "Default" (unless it is the active one, of course).

Touching inactive profiles goes against the concept of profiles itself, and surprises the user, or worse, breaks other profiles.

[ZetabS]

Thank you for the clarification @jest — I completely agree. I’ve updated the report accordingly.

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.