Agent Browser
Agent Browser is Vercel Labs' browser-automation CLI for agents. README now leads with a native Rust binary. Install is npm install -g agent-browser then agent-browser install (Chrome for Testing), or Homebrew / Cargo. The CLI is $0. Chrome, not a hosted browser seat, is what you run.
Compare Playwright if you wanted Microsoft's automation library, Cloudflare Computer if you wanted a hosted computer preview, and Cline if you wanted an editor agent that can call a browser tool.
Key Features
- Snapshot then click refs:
agent-browser snapshotreturns an accessibility tree with@e1refs. Clicks and fills use those refs. Traditional CSS / role selectors still work. - Rust first, source build is heavier: Global npm / Homebrew / Cargo install the native binary. Building from source wants Node.js 24+, pnpm 11+, and Rust. Do not call Node the runtime for the recommended install.
- Chrome for Testing: First-time
agent-browser installdownloads Google's automation Chrome. Existing Chrome, Brave, Playwright, and Puppeteer installs are detected. Linux can add--with-deps. - Not a Vercel dollar SKU: The repo is Apache-2.0. We did not find a public hosted-browser price on the README on the public page.
Use Cases
- People wiring a coding agent to a real page who want refs instead of brittle selectors.
- People comparing Agent Browser vs Playwright after they see 40,767 stars vs Playwright's library API.
- People who still think the product is a Node fallback CLI.
Limitation: We did not re-audit every command (pdf, annotate, CDP, serverless Chromium). Quality depends on the page and the agent that calls the CLI.
Pricing
github.com/vercel-labs/agent-browser on 2026-08-17.
| Piece | Price | Notes from first-party pages |
|---|---|---|
| agent-browser CLI | $0 | Apache-2.0. 40,767 stars. |
| Chrome for Testing | Downloaded locally | agent-browser install. |
| From source | $0 + toolchain | Node 24+, pnpm 11+, Rust. |
If a leftover page still says Node fallback is the product, treat this README as the source.
Getting Started
npm install -g agent-browserthenagent-browser install.agent-browser open example.comandagent-browser snapshot.- Click with
@e2from that snapshot, not a remembered selector. - Confirm Playwright if you wanted a library instead of a CLI.
Frequently Asked Questions
Is it still a Node CLI with a Rust option?
Recommended install is the native Rust binary. Node 24+ is for building from source.
Same as Playwright?
No. Playwright is a library. This is a CLI with snapshot refs for agents.
Is there a hosted Vercel price?
Not on the README on the public page. The software is Apache-2.0.
Alternatives
- Playwright: Microsoft browser automation, now with agent/MCP docs.
- Cloudflare Computer: Hosted computer preview, not this local CLI.
- Cline: Editor agent that can drive tools, including browsers.
Tips
- Quote 40,767 stars and Apache-2.0 from the GitHub check.
- Quote
snapshot+@eNrefs, not a Node-fallback census. - Confirm
agent-browser installbefore you assume system Chrome is enough.
Conclusion
Agent Browser is Vercel Labs' Apache-2.0 Rust CLI with 40,767 stars, not a Node-fallback product. Start at github.com/vercel-labs/agent-browser, then decide whether Playwright already covers the automation API you need.
Comments
No comments yet. Be the first to comment!
Related Tools
Related Insights
The Twilight of Low-Code Platforms: Why Claude Agent SDK Will Make Dify History
A deep dive from first principles of large language models on why Claude Agent SDK will replace Dify. Exploring why describing processes in natural language is more aligned with human primitive behavior patterns, and why this is the inevitable choice in the AI era.
Skills + Hooks + Plugins: How Anthropic Redefined AI Coding Tool Extensibility
An in-depth analysis of Claude Code's trinity architecture of Skills, Hooks, and Plugins. Explore why this design is more advanced than GitHub Copilot and Cursor, and how it redefines AI coding tool extensibility through open standards.
Stop Cramming AI Assistants into Chat Boxes: Clawdbot Picked the Wrong Battlefield
Clawdbot is convenient, but putting it inside Slack or Discord was the wrong design choice from day one. Chat tools are not for operating tasks, and AI isn't for chatting.