Feature Request: Optional auto-launch Chrome for Claude in Chrome integration

[shostako]

Summary

Currently, the "Claude in Chrome" feature requires users to manually launch Chrome before Claude Code can connect via the browser extension. This proposal suggests adding an optional auto-launch capability with user consent.

Current Behavior

• User must manually open Chrome before using Claude in Chrome
• If Chrome is not running, Claude Code cannot connect to the browser extension
• This creates friction in automated workflows and reduces convenience

Proposed Behavior

Add an optional setting or prompt that allows Claude Code to automatically launch Chrome when:

1. The user has explicitly enabled this feature in settings, OR
2. Claude Code prompts for one-time permission when Chrome is needed but not running

Rationale

Convenience

• Eliminates manual step in browser automation workflows
• Better integration for users who frequently use Claude in Chrome
• Smoother experience compared to requiring manual Chrome launch

Context Efficiency

• Claude in Chrome is a native Claude Code feature (not an MCP server)
• Avoiding the need for separate MCP-based browser automation (Puppeteer/Playwright) can reduce context overhead
• Native integration should be as frictionless as possible

Security Considerations

• User consent is key: Auto-launch would only occur after explicit user permission
• Could be implemented as:
  • A global setting: claude config set chrome.autoLaunch true
  • A per-session prompt: "Chrome is not running. Launch it now? (Y/n)"
• Users who prefer manual control can keep this disabled (default)

Differentiation from Puppeteer/Playwright

• The main advantage of Claude in Chrome is access to the user's logged-in session, cookies, and extensions
• If users still need to manually manage Chrome, this advantage is partially diminished
• Auto-launch would make the "use your real browser" experience truly seamless

Implementation Ideas

1. Setting-based: Add chrome.autoLaunch config option
2. Prompt-based: When connection fails, offer to launch Chrome with user confirmation
3. Profile selection: Optionally allow specifying which Chrome profile to launch

Additional Context

• This would maintain the security model (user must still approve sites in the extension)
• The auto-launch would simply start Chrome, not bypass any permission checks
• Users concerned about security can leave this feature disabled

[wimpywarlord]

+1 distrupts all my workflows - I use ZEN