[Bug] Claude Code MCP server fails to connect Chrome extension native host bridge socket

Bug Description
Title: Claude Code MCP server fails to connect to Chrome extension native host bridge socket

Environment:

• Claude Code: 2.1.109 (Homebrew cask, arm64)
• macOS: 26.2 (Darwin 25.2.0, Build 25C56)
• Chrome: 147.0.7727.102 (arm64)
• Claude Extension: 1.0.69
• Chrome Profile: Default
• Auth: claude.ai (Max subscription)

Description:
Chrome extension's native host process spawns correctly and creates a Unix socket at
/tmp/claude-mcp-browser-bridge-pakorns/<PID>.sock, but the Claude Code MCP server never connects
to it. mcp__claude-in-chrome__tabs_context_mcp always returns "Browser extension is not
connected."

What works:

• Chrome spawns native host correctly (claude --chrome-native-host, parent = Chrome)
• Bridge socket is created and listening
• Extension has nativeMessaging permission
• Extension installed and enabled in Default profile
• claude.ai logged in with same account as Claude Code

What doesn't work:

• Claude Code process has no socket connection to the bridge socket (verified via lsof)
• Multiple restart sequences tried (Chrome first, Claude Code first, both simultaneously)

Investigation details:

• Originally had both com.anthropic.claude_browser_extension.json (Desktop) and

com.anthropic.claude_code_browser_extension.json (Code) in NativeMessagingHosts/

• Renamed Desktop config to .disabled — extension falls through to Code host successfully
• Extension service worker tries Desktop host first, then Code host (confirmed in source)
• Native host creates socket, but MCP server in Claude Code session never connects to it

Steps to reproduce:

1. Have Claude Desktop installed (creates competing native messaging host)
2. Rename Desktop host config: com.anthropic.claude_browser_extension.json → .json.disabled
3. Restart Chrome, then start Claude Code
4. Call mcp__claude-in-chrome__tabs_context_mcp → "not connected"

Expected: MCP server connects to bridge socket and browser tools work.

Actual: Perpetual "Browser extension is not connected" despite native host running and socket
available.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.109
• Feedback ID: 1bf41a59-35fa-46e6-965a-ddce2de8224b