agent browser
- Repo stars 34,087
- Author repo agent-browser
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @vercel-labs · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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
This file is a discovery stub, not the usage guide. Before running any
`agent-browser` command, load the actual workflow content from the CLI:
```bash
agent-browser skills get core # start here — workflows, common patterns, troubleshooting
agent-browser skills get core --full # include full command reference and templates
```
The 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
Load a specialized skill when the task falls outside browser web pages:
```bash
agent-browser skills get electron # Electron desktop apps (VS Code, Slack, Discord, Figma, ...)
agent-browser skills get slack # Slack workspace automation
agent-browser skills get dogfood # Exploratory testing / QA / bug hunts
agent-browser skills get vercel-sandbox # agent-browser inside Vercel Sandbox microVMs
agent-browser skills get agentcore # AWS Bedrock AgentCore cloud browsers
```
Run `agent-browser skills list` to see everything available on the
installed version.
## 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
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.
Sections and files
Listed in source order.
sections -> Start here → Specialized skills → Why agent-browser → Observability Dashboard
terms -> Fast browser automation CLI for AI agents. · This file is a discovery stub, not the usage guide. · The CLI serves skill content that always matches the installed version, so instructions never go stale. · Run agent-browser skills list to see everything available on the installed version.
files/cmd -> @eN · npm i -g agent-browser && agent-browser install · agent-browser · skills get core · agent-browser skills list · https://dashboard.agent-browser.localhost
body sha256 -> 3b93c09eee36
Start here
This file is a discovery stub, not the usage guide. Before running any
agent-browsercommand, load the actual workflow content from the CLI: The 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 atskills get core.Specialized skills
Load a specialized skill when the task falls outside browser web pages: Run
agent-browser skills listto see everything available on the installed version.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
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.