Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Claude in Chrome: CLI never connects to native-host bridge socket (macOS, v2.1.121) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54212•Fetched 2026-04-29 06:33:18
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
ppikulappikula
Participants
github-actions[bot]github-actions[bot]ppikulappikula
Timeline (top)
labeled ×3commented ×1cross-referenced ×1

Code Example

Browser extension is not connected. Please ensure the Claude browser extension is installed and running...
RAW_BUFFERClick to expand / collapse

Environment

  • macOS 26.3 (Darwin 25.3.0 arm64)
  • Claude Code: 2.1.121
  • Chrome extension: 1.0.69 (ID fcoeoabgfenejglbffodgkkbkcdhcgfn)
  • Google Chrome: 148.0.7778.56
  • Both Claude Desktop and Claude Code installed

Symptom

Every mcp__claude-in-chrome__* tool call returns:

Browser extension is not connected. Please ensure the Claude browser extension is installed and running...

What works

  • Chrome → native host: when the extension wakes, Chrome successfully spawns claude.exe --chrome-native-host, which binds to /tmp/claude-mcp-browser-bridge-$USER/<pid>.sock (mode 0600, dir 0700).
  • The disconnect message correctly indicates the bridge isn't connected.

What doesn't work

  • The claude --chrome CLI session never opens a client connection to the bridge socket. lsof -p <claude-pid> shows no fd for /tmp/claude-mcp-browser-bridge-*.

Steps tried (all clean, none fixed it)

  1. Renamed Claude Desktop's com.anthropic.claude_browser_extension.json → .disabled (per a Reddit fix that worked for others).
  2. Fully quit & reopened Chrome.
  3. Uninstalled and reinstalled the Chrome extension.
  4. Updated Claude Code 2.1.119 → 2.1.121.
  5. Killed the native-host process so Chrome respawns it on the new binary; cleaned stale .sock files.
  6. Started multiple fresh claude --chrome sessions after each step.
  7. Removed com.apple.quarantine xattr from the bridge directory.
  8. Verified socket dir mode 0700, socket mode 0600.

Notes

  • Result is the same whether the Desktop host config is enabled or disabled.
  • Native host and CLI are both running the same binary path / version 2.1.121, so it isn't a version skew.
  • Happy to provide debug logs if there's a flag/path that surfaces the CLI's bridge-connection attempts (--debug doesn't appear to surface them).

extent analysis

TL;DR

The issue is likely due to the claude --chrome CLI session failing to connect to the bridge socket, and a potential workaround is to investigate the bridge connection attempts in the CLI.

Guidance

  • Verify the bridge socket file exists and has the correct permissions by running ls -l /tmp/claude-mcp-browser-bridge-$USER/ to check the file mode and directory mode.
  • Check if the claude --chrome CLI session is attempting to connect to the bridge socket by running the command with a verbose flag, if available, or by checking the debug logs.
  • Investigate potential issues with the socket file path or the CLI's ability to connect to the socket, such as file system permissions or configuration issues.
  • Consider providing debug logs from the claude --chrome CLI session to help diagnose the issue, if a flag or path is available to surface the bridge-connection attempts.

Notes

The issue may be related to the specific configuration or environment, and providing more information about the debug logs or the bridge connection attempts may help resolve the issue.

Recommendation

Apply workaround: Investigate the bridge connection attempts in the CLI to better understand the issue and potential solutions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING