Claude in Chrome: Allow browser selection instead of opening default browser

[kerim-ca]

What's Wrong?

When trying to manage permissions or reconnect Claude in Chrome, it opens the default browser. The default browser may not actually be Chrome - it may be a Chromium browser like Brave or another browser entirely. This means the Claude in Chrome extension may not be installed in the browser that opens.

What Should Happen?

Users should be able to choose which specific browser to open for Claude in Chrome connections, instead of always opening the default browser.

Error Messages/Logs

N/A - no errors, just opens wrong browser

Steps to Reproduce

1. Have Claude in Chrome extension installed in Chrome
2. Have a different browser set as system default (e.g., Brave)
3. Try to manage permissions or reconnect in Claude in Chrome from Claude Code
4. Default browser opens instead of Chrome where the extension is installed

Claude Model

N/A - this is a browser integration issue

Is this a regression?

No - this is about the Claude in Chrome (Beta) feature introduced in v2.0.72

Last Working Version

N/A - new feature

Claude Code Version

2.0.72 (Claude Code)

Operating System

• macOS (Darwin 24.5.0)
• Ubuntu Linux (also confirmed)

Terminal/Shell

• macOS: Apple Terminal with zsh
• Ubuntu: (terminal info not available)

Additional Information

Would like the ability to specify which browser to use for Claude in Chrome, rather than always opening the system default. Possible solutions:

• Add browser selection in /config
• Environment variable like CLAUDE_CHROME_BROWSER
• Prompt on first connection to choose preferred browser

[github-actions]

Found 2 possible duplicate issues:

1. [FEATURE] Detect Claude Chrome extension in other Chromium-based browsers #14370
2. Feature Request: Optional auto-launch Chrome for Claude in Chrome integration #14368

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[tarekbadrsh]

I have the same issue. Here are some workarounds I found:

Workaround	Pros	Cons
Temporarily change default browser	Works reliably	Annoying, affects whole system
Open Chrome manually first	Quick	Doesn't always work
Use Chrome DevTools MCP	Full control over browser path	More complex setup

Possible macOS Workaround

You could create a shell alias/script that temporarily sets Chrome as default, runs Claude, then restores Brave:

In your .zshrc or .bashrc

claude-chrome() {
# This is hacky but might work
open -a "Google Chrome" # Ensure Chrome is running first
sleep 1
claude --chrome "$@"
}

Or simply ensure Chrome is already open before running the autonomous agent—the extension should connect to the running Chrome instance.

Best practical advice for now: Keep Chrome open before running claude --chrome or the autonomous agent.

🤖 Generated with Claude Code

[wimpywarlord]

+1 distrupts all my workflows - I use ZEN

[idontdomath]

+1