claude --continue --chrome does not register the claude-in-chrome MCP server on resumed sessions

Environment

• Claude Code version: 2.1.220
• Platform: macOS (Darwin 25.5.0), Mac mini (Mac16,10)
• Claude in Chrome extension: v1.0.84 (latest at time of report), Chrome installed in /Applications
• Auth: claude.ai plan login (same account in CLI, extension, and claude.ai — verified in all three)
• Config: claudeInChromeDefaultEnabled: true set in ~/.claude.json; onboarding completed

Summary

The claude-in-chrome MCP server is never registered on resumed sessions — not via the enabled-by-default setting, and not even when explicitly passing --chrome to claude --continue. Brand-new sessions on the same machine with identical config register it and pair with the extension immediately.

Steps to reproduce

1. Machine with Claude in Chrome extension installed, paired, and working (verify: new claude session → "list my open Chrome tabs" succeeds).
2. Ensure Chrome integration is enabled by default (claudeInChromeDefaultEnabled: true in ~/.claude.json).
3. Exit an existing conversation and resume it: claude --continue --chrome
4. In the resumed session, check /mcp or attempt to use browser tools.

Expected

With --chrome passed explicitly (and/or enabled-by-default set), the resumed session registers the claude-in-chrome MCP server and its tools (list_connected_browsers, tabs_context_mcp, etc.) are available.

Actual

• The claude-in-chrome server is not listed in /mcp at all in the resumed session.
• Its mcp__claude-in-chrome__* tools are not registered (deferred-tool search returns no match).
• Before discovering the flag, tools in an older long-running session returned "Browser extension is not connected" on every attempt (6+ retries over ~30 min), while a brand-new session connected instantly — so retrying within a session never recovers.
• Result is the same whether resuming with or without --chrome.

Notes

• Extension-side configuration was exhaustively ruled out: correct extension (Claude in Chrome, not the sidebar), same account in extension popup / claude.ai / Chrome profile, Chrome fully restarted, extension force-update checked. App Translocation was also ruled out (a fresh session paired while Chrome was still translocated).
• Docs/help suggest --chrome is the way to enable the integration on a given launch; there is no indication resumed sessions are excluded. If this is intended, a startup warning ("--chrome has no effect with --continue") would save users a long debugging session.
• Minor related docs issue: guidance circulating suggests "enableChrome": true in settings.json; that key does not exist in the v2.1.220 settings schema — the real persistent toggle appears to be claudeInChromeDefaultEnabled in ~/.claude.json (set via /chrome).