VS Code extension launches the CLI without --chrome, so claude-in-chrome tools are never available in sidebar sessions

Summary

The VS Code extension launches the Claude Code binary without --chrome, so the claude-in-chrome MCP server is never loaded in sidebar sessions. Browser tools are therefore unavailable in the extension UI, even with the Claude in Chrome extension installed, connected and working.

This contradicts the documentation, which states:

In the VS Code extension, Chrome is available whenever the Chrome extension is installed. No additional flag is needed. (https://code.claude.com/docs/en/chrome)

Environment

• Windows 11 Pro 26200
• Claude Code CLI 2.1.270 (native install, ~/.local/bin/claude.exe)
• VS Code extension anthropic.claude-code 2.1.273 (bundled binary 2.1.272)
• Google Chrome 152.0.7977.83
• Claude in Chrome extension 1.0.93, installed and enabled in the active profile
• Signed in with /login (no API key, no setup-token)

Evidence

Command line of the process the sidebar UI spawns:

...\.vscode\extensions\anthropic.claude-code-2.1.272-win32-x64\resources\native-binary\claude.exe
  --output-format stream-json --verbose --input-format stream-json --max-thinking-tokens 3199

No --chrome. Consequences observed in every sidebar session: mcp__claude-in-chrome__* tools are absent, /mcp does not list claude-in-chrome, and the /chrome command does not exist.

Test matrix, same machine, same Chrome window, same account, identical prompt asking the model to call mcp__claude-in-chrome__list_connected_browsers and paste the literal result:

| Invocation | Result |
| --- | --- |
| claude --chrome -p ... (CLI 2.1.270) | [{"deviceId":"...","name":"Browser 1","osPlatform":"Windows","connectedAt":...,"isLocal":true}] |
| claude -p ... (CLI 2.1.270, no flag) | tool not available |
| extension binary 2.1.272, --chrome -p ... | browser connected, same JSON |
| extension binary 2.1.272, -p ... (no flag) | tool not available |

So the bundled binary supports the integration fine. Only the flag is missing from the way the extension invokes it.

Things that are not the cause

• Extension pairing. The native messaging host and the browser connection are healthy; the CLI reaches the same browser instantly.
• Claude Desktop. Its native host (chrome-native-host.exe under Roaming/Claude) starts on Chrome launch even with Desktop closed, and does not block Claude Code.
• claudeInChromeDefaultEnabled: true in ~/.claude.json, which is already set here and has no effect on sidebar sessions. Adding claudeInChromeEnabled: true also changed nothing (tested on both binaries, then reverted).

Expected behavior

Either the extension passes --chrome when Chrome integration is enabled, or it exposes a setting to enable it. Today the only extension setting that comes close is claudeCode.environmentVariables, and the binary has no environment variable that turns the integration on.

Workaround

Run claude --chrome in the VS Code integrated terminal. Resuming a sidebar session from that terminal also works and keeps the conversation.