Support --chrome flag for Claude MCP server integration

[Roasbeef]

Summary

Add support for the --chrome flag when creating new chat conversations, enabling the Claude MCP server integration.

Background

The Claude CLI supports a --chrome flag that enables the Chrome MCP server, allowing Claude to interact with browser automation capabilities. Currently, the plugin doesn't expose this option when spawning Claude conversations.

Proposed Solution

Add a setting or per-conversation option to enable the --chrome flag when calling the Agent SDK's query() function.

Implementation Options

Option A: Global Setting
Add a toggle in plugin settings:

// In SettingsTab.ts
chromeMcpEnabled: boolean; // "Enable Chrome MCP server"

Option B: Per-Conversation Flag
Add a command or input prefix to start a conversation with Chrome MCP:

• Slash command: /new-chrome or /chrome
• Setting toggle when creating new conversation

Option C: Both
Global default with per-conversation override.

Technical Details

The Agent SDK's query() function would need to pass through CLI arguments. This may require:

1. Checking if the SDK supports passing arbitrary CLI flags
2. Or using a different invocation method

Use Cases

• Web scraping and research tasks
• Automated browser interactions
• Testing web applications
• Gathering live data from websites

Related

• Claude CLI --chrome documentation
• MCP server architecture