Support configurable Chrome binary path for --chrome flag

Summary

The --chrome / /chrome integration currently hardcodes "Google Chrome" as the browser application name on macOS (via open -a "Google Chrome"). This makes it impossible to use Chrome Canary or other Chromium-based browsers with the Chrome integration feature.

Current Behavior

• Claude Desktop App uses hardcoded open -a "Google Chrome" to launch the browser
• The native messaging host config can be copied to Chrome Canary's NativeMessagingHosts/ directory
• The Claude in Chrome extension can be installed in Chrome Canary
• But /chrome always launches regular Google Chrome, ignoring Canary

Expected Behavior

Users should be able to configure which Chrome-based browser is used for the --chrome integration. Options could include:

• A setting in settings.json (e.g., "chromeBinary": "Google Chrome Canary")
• An environment variable (e.g., CLAUDE_CHROME_APP="Google Chrome Canary")
• Auto-detection of available Chrome variants with preference ordering

Environment

• macOS (Darwin 25.3.0)
• Claude Code CLI + Claude Desktop App
• Both Google Chrome and Google Chrome Canary installed
• Native messaging host config present for both browsers
• Claude in Chrome extension installed in Chrome Canary

Workaround

Currently none that fully works. The hardcoded path in the app binary (/Applications/Claude.app/Contents/Resources/app.asar) prevents redirection to Canary.

🤖 Generated with Claude Code