Unable to connect Claude from terminal to Chrome
I'm using Brave mainly for browsing and I have chrome on the side for debugging, installed the extension on chrome however Claude is never able to connect to Chrome, even when I use /chrome and reconnect, it opens chrome correctly and logs in but still not connecting
Env
- Claude Code CLI: 2.1.114
- macOS: 26.4.1 (25E253)
- Chrome: 147.0.7727.56
- Shell: zsh
Symptom
- mcp__claude-in-chrome__tabs_context_mcp (with and without createIfEmpty: true) returns: "Browser extension is not connected. Please ensure the Claude browser extension is installed..."
- /chrome → reconnect completed, opened claude.ai tab, already logged in. Still fails.
State observed
- Native messaging manifest present: ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json → allowed origin
chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/
- Wrapper script present: ~/.claude/chrome/chrome-native-host → exec .../2.1.114 --chrome-native-host
- Native host process IS running, spawned by Chrome: PID 4320, PPID 4065 (Google Chrome), uptime 4m34s at time of check
- Unix socket open: /tmp/claude-mcp-browser-bridge-amer/4320.sock (srw------- amer:wheel)
- CLI env: CLAUDE_CODE_SSE_PORT=15414, CLAUDECODE=1
Interpretation
Chrome DID launch the native host (extension installed + handshake with Chrome OK). Native host holds the bridge socket. But the MCP tool still reports "extension not connected" →
disconnect between CLI ↔ native-host bridge or extension ↔ native-host stdio channel, not a missing-extension problem. Possibly:
- Extension loaded but native port (chrome.runtime.connectNative) not connected / errored silently
- CLI can't locate /tmp/claude-mcp-browser-bridge-amer/4320.sock (stale PID discovery, wrong path lookup)
- Version mismatch between extension manifest and CLI 2.1.114 bridge protocol
Repro
- Fresh Claude Code 2.1.114 session
- Run /chrome → reconnect → Chrome opens, logged into claude.ai
- Call any mcp__claude-in-chrome__* tool → "extension not connected"
- lsof -p <native-host-pid> shows socket alive the whole time
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗