claude-code - 💡(How to fix) Fix [BUG] Brave not selectable in /chrome browser picker — reconnect opens & authorizes Brave but it never appears as a selectable browser

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…

Brave worked reliably with the Chrome integration for ~a month. After the update that added browser selection, Brave no longer appears in the picker, so no browser actions run — even though reconnecting still successfully opens and authorizes Brave. Appears to be a regression in the picker, not a connection failure.

Root Cause

Brave worked reliably with the Chrome integration for ~a month. After the update that added browser selection, Brave no longer appears in the picker, so no browser actions run — even though reconnecting still successfully opens and authorizes Brave. Appears to be a regression in the picker, not a connection failure.

RAW_BUFFERClick to expand / collapse

Environment

  • Claude Code v2.1.157 (CLI)
  • macOS 15.1 (24B2083), Apple Silicon
  • Brave 148.1.90.128 (Chromium); Claude in Chrome extension 1.0.74
  • Native messaging host present & intact: ~/Library/Application Support/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json

Summary

Brave worked reliably with the Chrome integration for ~a month. After the update that added browser selection, Brave no longer appears in the picker, so no browser actions run — even though reconnecting still successfully opens and authorizes Brave. Appears to be a regression in the picker, not a connection failure.

Steps to reproduce

  1. Brave (Chromium) with the Claude in Chrome extension installed + enabled.
  2. Run /chrome -> Reconnect extension -> Brave opens and authorizes successfully.
  3. Trigger a browser tool / browser selection.

Expected: A browser that authorized via reconnect is selectable (as Brave was before the picker). Actual: Brave is absent from the picker; list_connected_browsers returns []; no automation possible.

Note

Auth path still works for Brave; only the new picker filters it out. Possibly related: #34364, #14616. A config override for the browser allow-list would also resolve this.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Brave not selectable in /chrome browser picker — reconnect opens & authorizes Brave but it never appears as a selectable browser