Browser Automation with agent-browser

MANDATORY: Always use the agent-browser CLI for browser automation — do NOT use MCP chrome-devtools tools. To reuse an existing Chrome session, prefer agent-browser connect "${AGENT_BROWSER_CDP_PORT:-9222}" so later commands stay attached to the same browser; use --cdp <port> or --auto-connect for one-off calls.

Core Workflow

Every browser automation follows one of these patterns:

1. Fresh browser: agent-browser open <url> when the user wants a new ephemeral browser.
2. Reuse existing Chrome (preferred for logged-in state and fewer browser instances): agent-browser connect "${AGENT_BROWSER_CDP_PORT:-9222}"
3. Snapshot: agent-browser snapshot -i (get element refs like @e1, @e2)
4. Interact: Use refs to click, fill, select
5. Re-snapshot: After navigation or DOM changes, get fresh refs