
Agent Browser
- 8 installs
- 33 repo stars
- Updated April 26, 2026
- bighardperson/computer-science-skills-collection
agent-browser is a Claude Code skill wrapping the agent-browser CLI, a Rust-based headless browser automation tool that lets an agent navigate, click, type, and snapshot pages.
About
agent-browser is a skill wrapping the agent-browser CLI, a Rust-based headless browser automation tool with a Node.js fallback. A developer uses it so an agent can navigate pages, click, type, snapshot interactive elements, fill forms, and extract structured data via structured commands. It documents installation, the snapshot-then-interact workflow, and commands for screenshots, PDF, video, and semantic locators.
- Rust-based headless browser automation CLI with Node.js fallback
- navigate, click, type, snapshot, and interact via structured commands
- Semantic locators, screenshots, PDF export, and video recording
Agent Browser by the numbers
- 8 all-time installs (skills.sh)
- Ranked #1,522 of 2,719 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Jul 30, 2026 (Skillselion catalog sync)
Agent Browser capabilities & compatibility
Free and open source; installed via npm, requires Node.js and npm.
- Capabilities
- browser automation · web scraping · form filling · ui testing
- Works with
- playwright
- Use cases
- web scraping · testing · web search
- Platforms
- macOS · Linux
- Pricing
- Free
What Agent Browser says it does
A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured commands.
Snapshot: `agent-browser snapshot -i` (returns elements with refs like `@e1`, `@e2`)
Re-snapshot after navigation or significant DOM changes
npx skills add https://github.com/bighardperson/computer-science-skills-collection --skill agent-browserAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8 |
|---|---|
| repo stars | ★ 33 |
| Last updated | April 26, 2026 |
| Repository | bighardperson/computer-science-skills-collection ↗ |
What it does
Let an agent automate browser navigation, clicks, form fills, and page snapshots from the command line.
Who is it for?
Agent-driven web automation: navigating pages, filling forms, snapshotting elements, and extracting data.
Skip if: Environments without Node.js/npm, which the tool requires.
When should I use this skill?
Automating web interactions, extracting structured data, filling forms, or testing web UIs.
What you get
Deterministic browser actions driven by accessibility-tree snapshots and element refs.
- Browser navigation and interaction
- Page snapshots and extracted data
- Screenshots, PDF, and video output
By the numbers
- 4-step core workflow (navigate, snapshot, interact, re-snapshot)
Files
Browser Automation with agent-browser
Installation
npm recommended
npm install -g agent-browser
agent-browser install
agent-browser install --with-depsFrom Source
git clone https://github.com/vercel-labs/agent-browser
cd agent-browser
pnpm install
pnpm build
agent-browser installQuick start
agent-browser open <url> # Navigate to page
agent-browser snapshot -i # Get interactive elements with refs
agent-browser click @e1 # Click element by ref
agent-browser fill @e2 "text" # Fill input by ref
agent-browser close # Close browserCore workflow
1. Navigate: agent-browser open <url> 2. Snapshot: agent-browser snapshot -i (returns elements with refs like @e1, @e2) 3. Interact using refs from the snapshot 4. Re-snapshot after navigation or significant DOM changes
Commands
Navigation
agent-browser open <url> # Navigate to URL
agent-browser back # Go back
agent-browser forward # Go forward
agent-browser reload # Reload page
agent-browser close # Close browserSnapshot (page analysis)
agent-browser snapshot # Full accessibility tree
agent-browser snapshot -i # Interactive elements only (recommended)
agent-browser snapshot -c # Compact output
agent-browser snapshot -d 3 # Limit depth to 3
agent-browser snapshot -s "#main" # Scope to CSS selectorInteractions (use @refs from snapshot)
agent-browser click @e1 # Click
agent-browser dblclick @e1 # Double-click
agent-browser focus @e1 # Focus element
agent-browser fill @e2 "text" # Clear and type
agent-browser type @e2 "text" # Type without clearing
agent-browser press Enter # Press key
agent-browser press Control+a # Key combination
agent-browser keydown Shift # Hold key down
agent-browser keyup Shift # Release key
agent-browser hover @e1 # Hover
agent-browser check @e1 # Check checkbox
agent-browser uncheck @e1 # Uncheck checkbox
agent-browser select @e1 "value" # Select dropdown
agent-browser scroll down 500 # Scroll page
agent-browser scrollintoview @e1 # Scroll element into view
agent-browser drag @e1 @e2 # Drag and drop
agent-browser upload @e1 file.pdf # Upload filesGet information
agent-browser get text @e1 # Get element text
agent-browser get html @e1 # Get innerHTML
agent-browser get value @e1 # Get input value
agent-browser get attr @e1 href # Get attribute
agent-browser get title # Get page title
agent-browser get url # Get current URL
agent-browser get count ".item" # Count matching elements
agent-browser get box @e1 # Get bounding boxCheck state
agent-browser is visible @e1 # Check if visible
agent-browser is enabled @e1 # Check if enabled
agent-browser is checked @e1 # Check if checkedScreenshots & PDF
agent-browser screenshot # Screenshot to stdout
agent-browser screenshot path.png # Save to file
agent-browser screenshot --full # Full page
agent-browser pdf output.pdf # Save as PDFVideo recording
agent-browser record start ./demo.webm # Start recording (uses current URL + state)
agent-browser click @e1 # Perform actions
agent-browser record stop # Stop and save video
agent-browser record restart ./take2.webm # Stop current + start new recordingRecording creates a fresh context but preserves cookies/storage from your session. If no URL is provided, it automatically returns to your current page. For smooth demos, explore first, then start recording.
Wait
agent-browser wait @e1 # Wait for element
agent-browser wait 2000 # Wait milliseconds
agent-browser wait --text "Success" # Wait for text
agent-browser wait --url "/dashboard" # Wait for URL pattern
agent-browser wait --load networkidle # Wait for network idle
agent-browser wait --fn "window.ready" # Wait for JS conditionMouse control
agent-browser mouse move 100 200 # Move mouse
agent-browser mouse down left # Press button
agent-browser mouse up left # Release button
agent-browser mouse wheel 100 # Scroll wheelSemantic locators (alternative to refs)
agent-browser find role button click --name "Submit"
agent-browser find text "Sign In" click
agent-browser find label "Email" fill "user@test.com"
agent-browser find first ".item" click
agent-browser find nth 2 "a" textBrowser settings
agent-browser set viewport 1920 1080 # Set viewport size
agent-browser set device "iPhone 14" # Emulate device
agent-browser set geo 37.7749 -122.4194 # Set geolocation
agent-browser set offline on # Toggle offline mode
agent-browser set headers '{"X-Key":"v"}' # Extra HTTP headers
agent-browser set credentials user pass # HTTP basic auth
agent-browser set media dark # Emulate color schemeCookies & Storage
agent-browser cookies # Get all cookies
agent-browser cookies set name value # Set cookie
agent-browser cookies clear # Clear cookies
agent-browser storage local # Get all localStorage
agent-browser storage local key # Get specific key
agent-browser storage local set k v # Set value
agent-browser storage local clear # Clear allNetwork
agent-browser network route <url> # Intercept requests
agent-browser network route <url> --abort # Block requests
agent-browser network route <url> --body '{}' # Mock response
agent-browser network unroute [url] # Remove routes
agent-browser network requests # View tracked requests
agent-browser network requests --filter api # Filter requestsTabs & Windows
agent-browser tab # List tabs
agent-browser tab new [url] # New tab
agent-browser tab 2 # Switch to tab
agent-browser tab close # Close tab
agent-browser window new # New windowFrames
agent-browser frame "#iframe" # Switch to iframe
agent-browser frame main # Back to main frameDialogs
agent-browser dialog accept [text] # Accept dialog
agent-browser dialog dismiss # Dismiss dialogJavaScript
agent-browser eval "document.title" # Run JavaScriptState management
agent-browser state save auth.json # Save session state
agent-browser state load auth.json # Load saved stateExample: Form submission
agent-browser open https://example.com/form
agent-browser snapshot -i
# Output shows: textbox "Email" [ref=e1], textbox "Password" [ref=e2], button "Submit" [ref=e3]
agent-browser fill @e1 "user@example.com"
agent-browser fill @e2 "password123"
agent-browser click @e3
agent-browser wait --load networkidle
agent-browser snapshot -i # Check resultExample: Authentication with saved state
# Login once
agent-browser open https://app.example.com/login
agent-browser snapshot -i
agent-browser fill @e1 "username"
agent-browser fill @e2 "password"
agent-browser click @e3
agent-browser wait --url "/dashboard"
agent-browser state save auth.json
# Later sessions: load saved state
agent-browser state load auth.json
agent-browser open https://app.example.com/dashboardSessions (parallel browsers)
agent-browser --session test1 open site-a.com
agent-browser --session test2 open site-b.com
agent-browser session listJSON output (for parsing)
Add --json for machine-readable output:
agent-browser snapshot -i --json
agent-browser get text @e1 --jsonDebugging
agent-browser open example.com --headed # Show browser window
agent-browser console # View console messages
agent-browser console --clear # Clear console
agent-browser errors # View page errors
agent-browser errors --clear # Clear errors
agent-browser highlight @e1 # Highlight element
agent-browser trace start # Start recording trace
agent-browser trace stop trace.zip # Stop and save trace
agent-browser record start ./debug.webm # Record from current page
agent-browser record stop # Save recording
agent-browser --cdp 9222 snapshot # Connect via CDPTroubleshooting
- If the command is not found on Linux ARM64, use the full path in the bin folder.
- If an element is not found, use snapshot to find the correct ref.
- If the page is not loaded, add a wait command after navigation.
- Use --headed to see the browser window for debugging.
Options
- --session <name> uses an isolated session.
- --json provides JSON output.
- --full takes a full page screenshot.
- --headed shows the browser window.
- --timeout sets the command timeout in milliseconds.
- --cdp <port> connects via Chrome DevTools Protocol.
Notes
- Refs are stable per page load but change on navigation.
- Always snapshot after navigation to get new refs.
- Use fill instead of type for input fields to ensure existing text is cleared.
Reporting Issues
- Skill issues: Open an issue at https://github.com/TheSethRose/Agent-Browser-CLI
- agent-browser CLI issues: Open an issue at https://github.com/vercel-labs/agent-browser
{
"ownerId": "kn72ce44tqw8bnnnewrn1s5x3s7yz7sq",
"slug": "agent-browser",
"version": "0.2.0",
"publishedAt": 1768882342488
}{
"slug": "agent-browser",
"name": "Agent Browser",
"version": "0.2.0",
"installedAt": 1776152107477,
"source": "skillhub"
}Contributing to Agent Browser Skill
This skill wraps the agent-browser CLI. Determine where the problem lies before reporting issues.
Issue Reporting Guide
Open an issue in this repository if
- The skill documentation is unclear or missing
- Examples in SKILL.md do not work
- You need help using the CLI with this skill wrapper
- The skill is missing a command or feature
Open an issue at the agent-browser repository if
- The CLI crashes or throws errors
- Commands do not behave as documented
- You found a bug in the browser automation
- You need a new feature in the CLI
Before Opening an Issue
1. Install the latest version
npm install -g agent-browser@latest2. Test the command in your terminal to isolate the issue
Issue Report Template
Use this template to provide necessary information.
### Description
[Provide a clear and concise description of the bug]
### Reproduction Steps
1. [First Step]
2. [Second Step]
3. [Observe error]
### Expected Behavior
[Describe what you expected to happen]
### Environment Details
- **Skill Version:** [e.g. 1.0.2]
- **agent-browser Version:** [output of agent-browser --version]
- **Node.js Version:** [output of node -v]
- **Operating System:** [e.g. macOS Sonoma, Windows 11, Ubuntu 22.04]
### Additional Context
- [Full error output or stack trace]
- [Screenshots]
- [Website URLs where the failure occurred]Adding New Commands to the Skill
Update SKILL.md when the upstream CLI adds new commands.
- Keep the Installation section
- Add new commands in the correct category
- Include usage examples
Related skills
FAQ
How is it installed?
npm install -g agent-browser, then agent-browser install (recommended), or build from source.
What is the core workflow?
Navigate, snapshot interactive elements to get refs like @e1, interact using those refs, then re-snapshot after DOM changes.