agent-browser
Automate browser interaction, screenshots, extraction and web QA; also Electron apps, Slack UI workflows, and browsers in Vercel Sandbox or Bedrock AgentCore. Use when the task needs browser control.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- agent-browser
- hidden
- true
- description
- Automate browser interaction, screenshots, extraction and web QA; also Electron apps, Slack UI workflows, and browsers in Vercel Sandbox or Bedrock AgentCore. Use when the task needs browser control.
- allowed-tools
- Bash(agent-browser:*), Bash(npx agent-browser:*)
02 资源文件 2
- 参考文档agents/openai.yaml42 B
- 许可证LICENSE10.7 KB
03 SKILL.md 正文
agent-browser
Modified by CXPhoenix for harness-agile: compact discovery, evidence-equivalent native browser tools, and explicit authorization boundaries (2026-09-12). Upstream source and Apache-2.0 license: see LICENSE and docs/agents/skill-sources.json in the project root. License restoration: 2026-09-13.
Fast browser automation CLI for AI agents. Chrome/Chromium via CDP with
accessibility-tree snapshots and compact @eN element refs.
Use available native browser tools instead when they satisfy the requested surface and evidence requirements, unless the user specifically requires agent-browser. This skill provides tool usage guidance, not authorization to send messages or change external state. Existing user authorization and host permissions govern actions.
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 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:
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.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
wait-what
Stop. That last message did not land: re-pitch it.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.