/chrome command opens Brave instead of Chromium on Linux

Description

The /chrome command in Claude Code opens Brave browser instead of connecting to the already-running Chromium instance, even though:

• Default browser is set to Chromium (xdg-settings get default-web-browser → chromium.desktop)
• All HTTP/HTTPS scheme handlers point to chromium.desktop
• The Claude Code Chrome extension is installed only in Chromium (not Brave)
• Native messaging host configs exist for both browsers (identical content)
• Chromium is running; Brave is not

Environment

• OS: Arch Linux (kernel 6.19.10-arch1-1)
• Display: Wayland
• Claude Code version: 2.1.92
• Chromium version: 146.0.7680.177
• Brave: installed at /usr/bin/brave but not running
• Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn (v1.0.66)

Expected behavior

/chrome should connect to the running Chromium instance where the extension is installed.

Actual behavior

/chrome launches Brave browser instead.

Steps to reproduce

1. Have both Chromium and Brave installed on Arch Linux
2. Set Chromium as default browser
3. Install Claude Code Chrome extension in Chromium only
4. Open Chromium
5. Run /chrome in Claude Code CLI
6. Brave opens instead of connecting to Chromium

Notes

• Native messaging host configs are identical across ~/.config/chromium/, ~/.config/BraveSoftware/Brave-Browser/, and ~/.config/google-chrome/
• Suspect the /chrome command's browser detection logic picks up brave from $PATH before chromium, ignoring the default browser setting and where the extension is actually installed