Chrome extension: 'Browser extension is not connected' despite native host running

Environment

• Claude Code: 2.1.81
• Chrome: 146.0.7680.80
• Extension: Claude in Chrome (Beta) 1.0.63
• macOS Darwin 25.3.0 (Apple Silicon, 48GB RAM)
• Chrome Profile: Profile 8 (non-default "Work" profile)

Problem

mcp__claude-in-chrome__tabs_context_mcp always returns "Browser extension is not connected", even though everything appears correctly set up.

What works

• Native messaging host config exists at ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json
• Native host binary runs fine: creates socket at /tmp/claude-mcp-browser-bridge-<user>/<pid>.sock
• Socket file is present and native host process is running
• Extension is installed, enabled, service worker active (no errors in console)
• Claude Code was started with --chrome flag

What doesn't work

• tabs_context_mcp always returns "not connected"
• Using /chrome → "Reconnect extension" opens claude.ai and Chrome immediately crashes/closes
• Restarting Chrome, disabling/re-enabling extension, launching with specific profile flag — none help

Reproduction steps

1. Install Claude in Chrome extension (1.0.63)
2. Start Claude Code with --chrome
3. Run /chrome → select "Reconnect extension"
4. Chrome opens claude.ai tab then crashes
5. Reopen Chrome, try tabs_context_mcp → "not connected"

Notes

• Extension is installed in a non-default Chrome profile (Profile 8 / "Work")
• This might be a profile-related issue — the native messaging host config is global but perhaps the MCP bridge expects the default profile