Claude-in-Chrome: login succeeds but no browser ever connects (list_connected_browsers returns [], switch_browser finds no browsers)

Summary

Claude-in-Chrome extension is installed and claude.ai login succeeds, but the browser never becomes reachable for automation. Every connection path reports zero connected browsers, so pairing (switch_browser) has no target and no mcp__claude-in-chrome__* tool can run.

Environment

• Claude Code CLI (browser automation via mcp__claude-in-chrome__*)
• Platform: macOS (Darwin 25.5.0)
• gh account authenticated; claude.ai /login reported: Login successful. Remote Control disconnected.
• Extension reported as installed by the user

What happens

Diagnostic calls, all after a successful claude.ai login and with the extension installed:

| Call | Result |
| --- | --- |
| tabs_context_mcp (incl. createIfEmpty: true) | Browser extension is not connected... |
| list_connected_browsers | [] |
| switch_browser (pairing broadcast) | No other browsers available to switch to. |

switch_browser was invoked multiple times; it always returns "No other browsers available", because no extension instance is maintaining a session with the account — so the pairing prompt has no destination.

Expected

After installing the extension and logging in with the same account, list_connected_browsers should list the local Chrome instance (or switch_browser should be able to broadcast a pairing prompt to it).

Steps taken by the user (still failing)

1. Extension installed
2. claude.ai /login — succeeded (but message included Remote Control disconnected)
3. Retried pairing (switch_browser) several times

Notes

The failure is upstream of pairing: the extension does not appear to establish/maintain a connection to the account backend, so there is never a browser for the automation layer to attach to. Restarting Chrome and re-enabling "Connect" in the extension popup did not surface a connected browser to the tooling.