Issue in claude-in-chrome

claude-in-chrome MCP tools (e.g. tabs_context_mcp) consistently return "Browser extension is not connected" even though the extension is installed, enabled, and logged in.

Environment

• Claude Code CLI: 2.1.240 (Windows, installed via WinGet)
• Claude Chrome extension: 1.0.85
• OS: Windows 11 Home 10.0.26200

Troubleshooting already done

• Extension confirmed installed and enabled in chrome://extensions
• Extension side panel opens fine, logged into claude.ai (same account as CLI), and its own chat works (sent "Hi", got a response)
• Native messaging host manifests (com.anthropic.claude_code_browser_extension, com.anthropic.claude_browser_extension) are correctly registered in HKCU\Software\Google\Chrome\NativeMessagingHosts, paths on disk are valid
• Found and removed a stale daemon.lock referencing a dead PID from an older CLI version (2.1.203) — did not fix it
• Fully restarted Chrome and Claude Code multiple times
• Upgraded Claude Code CLI (2.1.203 → 2.1.229 → 2.1.240) — did not fix it
• TcpTestSucceeded: True connecting to bridge.claudeusercontent.com:443 — not a network/firewall issue
• Ran /plugin to reconnect the MCP server — MCP layer reconnects fine, but the extension↔daemon handshake still fails

Expected: tabs_context_mcp connects to the browser extension.
Actual: Always returns "Browser extension is not connected."