
Agent Browser
- 11 installs
- 11 repo stars
- Updated July 30, 2026
- builderio/builder-agent-skills
This is a copy of agent-browser by vercel-labs - installs and ranking accrue to the original listing.
agent-browser is a browser-automation CLI skill that drives Chrome/Chromium over CDP so AI agents can navigate, fill forms, screenshot, scrape, and test web and Electron apps.
About
A discovery-stub skill for agent-browser, a Rust CLI that automates Chrome/Chromium over CDP for AI agents. A developer uses it to navigate pages, fill forms, click, screenshot, scrape data, or test and QA web and Electron apps. The stub points the agent to load current workflow content via agent-browser skills get core.
- Browser automation CLI for AI agents using Chrome/Chromium via CDP
- Accessibility-tree snapshots with compact @eN element refs for reliable interaction
- Specialized skills for Electron apps, Slack, QA dogfooding, and cloud browsers
Agent Browser by the numbers
- 11 all-time installs (skills.sh)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
agent-browser capabilities & compatibility
- Capabilities
- web scraping · testing · web search
- Works with
- chrome · playwright · slack · vercel · aws
- Use cases
- web scraping · testing · web search
- IDEs
- cursor ide
- Pricing
- Free
What agent-browser says it does
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`
Chrome/Chromium via CDP with no Playwright or Puppeteer dependency
npx skills add https://github.com/builderio/builder-agent-skills --skill agent-browserAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 11 |
|---|---|
| repo stars | ★ 11 |
| Last updated | July 30, 2026 |
| Repository | builderio/builder-agent-skills ↗ |
What it does
Automate a browser or Electron app from an agent to fill forms, click, screenshot, scrape, or QA a web app.
Who is it for?
Agent-driven browser automation, exploratory testing, QA, and Electron desktop app control.
Skip if: Relying on the stub itself for commands - it says to load skills get core first.
When should I use this skill?
The user needs to open a website, fill a form, click, screenshot, scrape data, or test a web app.
What you get
The agent drives real Chrome sessions via CDP with accessibility-tree snapshots and element refs.
By the numbers
- Lists 5 specialized skills (electron, slack, dogfood, vercel-sandbox, agentcore)
- Dashboard runs on port 4848
Files
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:
agent-browser skills get core # start here — workflows, common patterns, troubleshooting
agent-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
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 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 browsersRun 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.
Related skills
FAQ
How do I install agent-browser?
Run npm i -g agent-browser && agent-browser install per the SKILL.md.
Does it need Playwright or Puppeteer?
No. It drives Chrome/Chromium via CDP with no Playwright or Puppeteer dependency.