Claude in Chrome stays disconnected after /login account switch mid-session; only /mcp reconnect + select_browser fixes it

Summary

After running /login mid-session to switch Claude Code to a different claude.ai account (the account the Claude in Chrome extension is signed into), the session could no longer reach the browser. list_connected_browsers returned [] and tabs_context_mcp returned "Browser extension is not connected", even though the accounts matched. Before the /login, the same session drove Chrome without problems.

What did NOT fix it

• /chrome (reconnect)
• Re-signing into the extension with the matching account
• Fully quitting and relaunching Chrome (Cmd+Q)

What fixed it

/mcp -> claude-in-chrome -> Reconnect. After that, list_connected_browsers returned the browser, but tabs_context_mcp still said "not connected" until select_browser was called with the listed deviceId. Then everything worked.

Expected

After /login, the claude-in-chrome MCP connection re-authenticates with the new account automatically, or /chrome -> Reconnect does it. The error message should point to /mcp reconnect when the session's MCP auth is stale.

Environment

• Claude Code 2.1.285, macOS (Darwin 25.5.0)
• Chrome with the Claude in Chrome extension; the Chrome profile's Google account differs from the extension's claude.ai account (intended)
• Claude Desktop is also installed. Its native host config com.anthropic.claude_browser_extension.json lists the same extension id (fcoeoabgfenejglbffodgkkbkcdhcgfn) as Claude Code's com.anthropic.claude_code_browser_extension.json.

Repro

1. Start a session with Chrome working.
2. Run /login and switch to another claude.ai account that the extension also uses.
3. Call any browser tool: "Browser extension is not connected"; list_connected_browsers returns [].
4. /chrome reconnect and a Chrome restart do not help; /mcp -> claude-in-chrome -> Reconnect plus select_browser does.