Agent Browser
agent-browser is an agent skill that exposes a Chromium CDP CLI for navigation, forms, screenshots, scraping, and QA-style browser automation.
npx skills add https://github.com/vercel-labs/agent-browser --skill agent-browser| Installs | 463k |
|---|---|
| GitHub stars | ★ 35.5k |
| Security audit | 2 / 3 scanners passed |
| Last updated | June 5, 2026 |
| Repository | vercel-labs/agent-browser ↗ |
What it does
You need your agent to complete real browser work—logins, flows, captures, or scrapes—but built-in web tools break on complex pages or lack stable element targeting.
Who is it for?
Solo builders who already run Claude Code or Cursor with shell access and want one CLI for QA, dogfooding, form flows, and light scraping on their own apps or staging sites.
Skip if: Teams that forbid shell/network browser automation, need official Playwright test suites in CI without agent involvement, or only want read-only docs with no live site interaction.
When should I use this skill?
User needs to interact with websites or Electron apps: navigate, forms, clicks, screenshots, scrape, test web apps, login, automate browser actions, exploratory QA, dogfooding, bug hunts, Slack automation, or Vercel Sand
What you get
You get repeatable Bash-driven browser sessions with workflow docs from the CLI, structured snapshots/refs, and outputs like screenshots or extracted page data.
- Browser session artifacts (screenshots, extracted page data)
- Completed UI flows (forms submitted, navigation steps executed)
- QA notes tied to reproducible CLI-driven browser actions
Related skills
Lark ApprovalTrigger, track, and manage Lark approval workflows from AI agents — submit approvals, check status, and react to approval decisions programmatically.253kLark CalendarRead and write Lark calendar events from AI agents — schedule meetings, check availability, and trigger workflows based on calendar data.252kLark DriveStore, retrieve, and share files in Lark Drive programmatically, similar to Google Drive.252kLark ContactManage and query the Lark contact/people directory — look up users, departments, and org structure via API.252kLark ImSend and read messages in Lark chat channels programmatically from your app or automation.252kLark AttendanceTrack and query employee attendance records in Lark programmatically for HR and operations automation.252kHow it compares
Use this Bash-first Chromium CLI instead of ad-hoc built-in browser tools when you need CDP snapshots, @eN refs, and the packaged `skills get core` workflows.
FAQ
Who is agent-browser for?
Indie and solo builders using AI coding agents who need reliable browser automation for their own web apps, landing pages, Electron tools, or internal QA—not a generic bookmark list.
When should I use agent-browser?
Use it when prompts ask to open a site, fill a form, click buttons, screenshot, scrape, test a web app, automate Slack/Electron, or run exploratory QA; it also fits Validate prototype checks and Build integration debugging before Ship-level bug hunts.
Is agent-browser safe to install?
It runs shell commands with network and full browser access—review the Security Audits panel on this Prism page, inspect the vercel-labs/agent-browser source, and only aim it at sites and credentials you trust.
SKILL.md
# 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.