Agent Browser
npx skills add marcusrbrown/systematic --skill agent-browseragent-browser
Section titled “agent-browser”Fast browser automation CLI for AI agents. Chrome/Chromium via CDP with accessibility-tree snapshots and compact @eN element refs.
Install: npm i -g agent-browser && agent-browser install
Start here
Section titled “Start here”This file is a discovery stub, not the usage guide. Before running any agent-browser command, load the actual workflow content from the CLI:
agent-browser skills get core # start here — workflows, common patterns, troubleshootingagent-browser skills get core --full # include full command reference and templatesThe CLI serves skill content that always matches the installed version, so instructions never go stale. The content in this stub cannot change between releases, which is why it just points at skills get core.
Specialized skills
Section titled “Specialized skills”Load a specialized skill when the task falls outside browser web pages:
agent-browser skills get electron # Electron desktop apps (VS Code, Slack, Discord, Figma, ...)agent-browser skills get slack # Slack workspace automationagent-browser skills get dogfood # Exploratory testing / QA / bug huntsagent-browser skills get derive-client # Record a HAR, derive a standalone API client for a siteagent-browser skills get vercel-sandbox # agent-browser inside Vercel Sandbox microVMsagent-browser skills get agentcore # AWS Bedrock AgentCore cloud browsersRun agent-browser skills list to see everything available on the installed version.
Why agent-browser
Section titled “Why agent-browser”- Fast native Rust CLI, not a Node.js wrapper
- Works with any AI agent (Cursor, Claude Code, Codex, Continue, Windsurf, etc.)
- Chrome/Chromium via CDP with no Playwright or Puppeteer dependency
- Accessibility-tree snapshots with element refs for reliable interaction
- Sessions, authentication vault, state persistence, video recording
- Specialized skills for Electron apps, Slack, exploratory testing, cloud providers
Observability Dashboard
Section titled “Observability Dashboard”The dashboard runs independently of browser sessions on port 4848 and can also be opened through a proxied or forwarded URL such as https://dashboard.agent-browser.localhost. Agents should stay on the dashboard origin: session tabs, status, and stream traffic are proxied internally, so session ports do not need to be exposed.