[BUG] Brave not selectable in /chrome browser picker — reconnect opens & authorizes Brave but it never appears as a selectable browser

Resolved 💬 1 comment Opened May 30, 2026 by qhansen628 Closed Jul 3, 2026

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.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗