browser-automation / cli
agent-browser
Capability: agent-browser
Use it when
- An AI agent needs to drive a real Chrome browser from shell commands, reading pages via accessibility-tree snapshots and clicking elements by stable refs instead of brittle CSS selectors
- Your automation keeps forcing re-login every run and you need saved auth state, Chrome profile reuse, or session persistence so the agent stays authenticated across restarts
What it solves
Not the fit when
- Bypassing bot detection, CAPTCHAs, or anti-scraping defenses
- Accessibility audits on Safari or iOS WebDriver sessions (a11y requires a CDP browser)
- High-volume distributed scraping behind provider rate limits
- bot-detection-challenge
- geo-block
- rate-limit-throttle
Install
npm install -g agent-browser && agent-browser install
Invoke
agent-browser open example.com; agent-browser snapshot; agent-browser click @e2; agent-browser fill @e3 "text"; or run agent-browser mcp for an MCP stdio server
Alternatives
No reviewed alternatives recorded yet.