Claude-in-Chrome: extension reports "not connected" persistently, even after Claude Code restart

Summary

The Claude-in-Chrome browser extension repeatedly fails to connect from Claude Code. Every mcp__claude-in-chrome__* call (starting with tabs_context_mcp) returns:

Browser extension is not connected. Please ensure the Claude browser extension is installed and running (https://claude.ai/chrome), and that you are logged into claude.ai with the same account as Claude Code.

The extension is installed and Chrome is logged into claude.ai with the same account.

Steps to reproduce

1. In Claude Code, ask Claude to do a browser task (drive mcp__claude-in-chrome__*).
2. Claude calls mcp__claude-in-chrome__tabs_context_mcp.
3. The call returns "Browser extension is not connected" instead of the tab context.

Expected

tabs_context_mcp returns the current MCP tab group / tab IDs so browser automation can proceed.

Actual

"Browser extension is not connected" on every attempt, including immediately after a fresh tabs_context_mcp call.

What I've already tried

• Restarting Claude Code (the extension still reports not connected after restart).
• Confirmed Chrome is running and signed into claude.ai on the same account as Claude Code.

The disconnect persists across a Claude Code restart, so it does not appear to be a transient startup race.

Impact

Blocks all Claude-in-Chrome automation. Workarounds (chrome-devtools-axi / chrome-devtools MCP) launch an isolated, unauthenticated Chrome profile, so they can't reach sites that require my existing logged-in session — which is the whole point of driving the real browser.

Environment

• Claude Code: 2.1.215
• OS: macOS 15.7.7
• Google Chrome: 150.0.7871.129