V
vercel-labs/agent-browser
Browser automation CLI for AI agents
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"vercel-labs-agent-browser": {
"command": "npx",
"args": ["skills"]
}
}
}Parsed from the README we fetched on 2026-11-05; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"vercel-labs-agent-browser": {
"command": "npx",
"args": ["skills"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio vercel-labs-agent-browser -- npx skills
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 50,657 ★ · vercel-labs/agent-browser · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-06 · last seen 2026-11-14 · seen 8× · listed by 1 sources
- Install
npx skills
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx skills. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We have no tags recorded for it yet.
Who maintains it?
repository
vercel-labs/agent-browser；first catalogued 2026-11-06；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# agent-browser
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Browser automation for AI agents: open pages, read them as an accessibility tree, and act on elements from the shell.
agent-browser is a native Rust CLI that gives an AI agent a browser it can drive one command at a time. snapshot returns the page as compact text with a ref such as @e1 for each element. The agent acts on a ref, reads the page again to check the result, and repeats. The browser stays open between commands, so each step is one short shell call.
## Install
bash
npm install -g agent-browser
agent-browser install # download Chrome for Testing (first time only)
Homebrew: brew install agent-browser, then agent-browser install.
Linux: agent-browser install --with-deps also installs the browser's system libraries.
No install: npx agent-browser open example.com.
Project installs, building from source, upgrade, and doctor are covered in Installation.
## Quick start
bash
agent-browser open example.com
agent-browser snapshot -i # interactive elements, each with a ref
agent-browser click @e1 # act on a ref from that snapshot
agent-browser get url # check the result
agent-browser close
The snapshot for example.com:
link "Learn more" [ref=e1]
Refs describe the page at the time of the snapshot. After navigation or a DOM change, take a new snapshot before using refs again.
CSS selectors, text, XPath, and semantic locators also work, for example agent-browser find role button click --name "Submit". See Selectors.
A click fails, instead of reporting success, when the target is hidden, disabled, outside the viewport, or covered by another element such as a consent banner. Dismiss the covering element, take a new snapshot, and retry.
The full walkthrough is in the quick start.
## How it works
The CLI sends each command to a background daemon that starts on the first command and controls the browser over the Chrome DevTools Protocol. Each --session gets its own daemon and browser. By default, the daemon closes a headless browser and exits after one hour without commands, saving state first when session persistence is configured.
Chrome for Testing is the default browser. You can also attach to a running Chrome with --cdp or --auto-connect (CDP mode), select the Lightpanda or Obscura engine with --engine, drive Mobile Safari in the iOS Simulator, or use a cloud browser provider such as Browserbase, Browserless, Browser Use, Kernel, or AgentCore.
## For AI agents
The CLI ships skills that match its version:
bash
agent-browser skills get core # the core loop, refs, waiting, and common workflows
agent-browser skills get core --ref commands # one reference, such as the full command list
agent-browser skills get core --full # adds the full command reference and templates
agent-browser skills list # specialized skills: electron, slack, dogfood, and more
Install the discovery skill into an agent harness from skills.sh:
bash
npx skills add vercel-labs/agent-browser
The installed skill is a thin stub that tells the agent to load agent-browser skills get core, so its instructions always match the installed CLI. Or add this to your AGENTS.md:
agent-browser is a native Rust CLI that gives an AI agent a browser it can drive one command at a time. snapshot returns the page as compact text with a ref such as @e1 for each element. The agent acts on a ref, reads the page again to check the result, and repeats. The browser stays open between commands, so each step is one short shell call.
## Install
bash
npm install -g agent-browser
agent-browser install # download Chrome for Testing (first time only)
Homebrew: brew install agent-browser, then agent-browser install.
Linux: agent-browser install --with-deps also installs the browser's system libraries.
No install: npx agent-browser open example.com.
Project installs, building from source, upgrade, and doctor are covered in Installation.
## Quick start
bash
agent-browser open example.com
agent-browser snapshot -i # interactive elements, each with a ref
agent-browser click @e1 # act on a ref from that snapshot
agent-browser get url # check the result
agent-browser close
The snapshot for example.com:
link "Learn more" [ref=e1]
Refs describe the page at the time of the snapshot. After navigation or a DOM change, take a new snapshot before using refs again.
CSS selectors, text, XPath, and semantic locators also work, for example agent-browser find role button click --name "Submit". See Selectors.
A click fails, instead of reporting success, when the target is hidden, disabled, outside the viewport, or covered by another element such as a consent banner. Dismiss the covering element, take a new snapshot, and retry.
The full walkthrough is in the quick start.
## How it works
The CLI sends each command to a background daemon that starts on the first command and controls the browser over the Chrome DevTools Protocol. Each --session gets its own daemon and browser. By default, the daemon closes a headless browser and exits after one hour without commands, saving state first when session persistence is configured.
Chrome for Testing is the default browser. You can also attach to a running Chrome with --cdp or --auto-connect (CDP mode), select the Lightpanda or Obscura engine with --engine, drive Mobile Safari in the iOS Simulator, or use a cloud browser provider such as Browserbase, Browserless, Browser Use, Kernel, or AgentCore.
## For AI agents
The CLI ships skills that match its version:
bash
agent-browser skills get core # the core loop, refs, waiting, and common workflows
agent-browser skills get core --ref commands # one reference, such as the full command list
agent-browser skills get core --full # adds the full command reference and templates
agent-browser skills list # specialized skills: electron, slack, dogfood, and more
Install the discovery skill into an agent harness from skills.sh:
bash
npx skills add vercel-labs/agent-browser
The installed skill is a thin stub that tells the agent to load agent-browser skills get core, so its instructions always match the installed CLI. Or add this to your AGENTS.md:
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/vercel-labs-agent-browser/)
- Source
- github · https://github.com/vercel-labs/agent-browser
- Traction
- 50,657 ★
- added
- today