[BUG] Regression in 2.1.153: claude-in-chrome browser tools no longer load in VS Code extension (worked in 2.1.152)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The mcp__claude-in-chrome__* browser tools stopped loading in the Claude Code VS Code extension chat panel after the extension auto-updated. I bisected the exact version where the regression landed:

• 2.1.152: working
• 2.1.153: broken
• 2.1.156 (current): still broken

Downgrading to 2.1.152 reliably restores the browser tools, so this is a clear regression introduced between 2.1.152 and 2.1.153.

Symptoms on 2.1.153 / 2.1.156:

• @browser:new_tab (and any @browser:*) does not resolve to any tool
• Claude reports that mcp__claude-in-chrome__ is not in the available tool list — only mcp__claude_ai_ and mcp__plugin_agents_hub_* are present
• /chrome returns "isn't available in this environment"
• The "Browser connected" banner is still shown, so the native connection is up, but the tools are never injected into the session
• claude --chrome from the integrated terminal works fine — the issue is specific to the VS Code extension chat panel

What Should Happen?

Browser tools (mcp__claude-in-chrome__) should be available in the VS Code extension chat panel, as they were on 2.1.152. @browser: mentions should resolve and Claude should be able to control Chrome.

Error Messages/Logs

No error shown in chat. Claude responds:
"I don't see browser automation tools (mcp__claude-in-chrome__*) available in this session — they weren't in the deferred tools list."

Steps to Reproduce

1. Windows, Claude Code VS Code extension on 2.1.153 or 2.1.156
2. Claude in Chrome extension installed and connected ("Browser connected" banner visible)
3. Open a new conversation in the VS Code extension chat panel
4. Type @browser:new_tab or ask Claude to open a Chrome tab
5. Browser tools are unavailable; /chrome returns "isn't available in this environment"
6. Downgrade the extension to 2.1.152 and repeat — tools work again

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.152

Claude Code Version

2.1.156

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

Issue persists across full VS Code restart and PC reboot.

Possibly related:

• #52879 (closed) — same symptoms, no fix
• #23939 (closed not planned) — root cause: claude-vscode MCP "-32601: Method not found"
• #58201 (open) — Windows native-host conflict