agent-browser

Automate browser navigation, form filling, screenshots, and data extraction via a CLI.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/AveryRen/WarpTalk-TestPayment --skill agent-browser-averyren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/AveryRen/WarpTalk-TestPayment/tree/main/agent/.agents/skills/agent-browser
Command: npx skills add https://github.com/AveryRen/WarpTalk-TestPayment --skill agent-browser-averyren

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, and includes references (resource) components.

What problem does it solve? Manually interacting with websites for testing, scraping, or repetitive workflows is slow and error-prone. This Skill gives AI agents programmatic control of a real browser through a simple CLI, enabling navigation, form submission, authentication, and content capture without writing custom automation code. ## Core Features & Use Cases - Snapshot-Based Interaction: Get compact element references (@e1, @e2) from accessibility-tree snapshots, then click, fill, select, and scroll using those refs with minimal token usage. - Authentication & Sessions: Handle logins via auth vault, persistent profiles, session state files, or importing cookies from an existing Chrome session, including OAuth and 2FA flows. - Capture & Verification: Take annotated screenshots, save pages as PDF, record video sessions, and diff page states or screenshots to verify changes. - Use Case: Test a web app's signup flow by opening the page, snapshotting the form, filling fields with refs, submitting, and diffing the result against a baseline screenshot. ## Quick Start Ask the agent to open a website with agent-browser, take an interactive snapshot, fill in the login form, and capture a screenshot of the result.

Frequently Asked Questions about agent-browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser actions with agent-browser?

Open a URL with agent-browser open, run snapshot -i to get element refs like @e1, then use click, fill, and select with those refs. Re-snapshot after any navigation or DOM change because refs are invalidated when the page changes.

How to handle login and authentication in browser automation?

Use the auth vault to store encrypted credentials and run agent-browser auth login, or save session state with state save and reload it later. You can also import cookies from a running Chrome instance via --auto-connect state save.

Does agent-browser support parallel browser sessions?

Yes, use the --session flag to run isolated sessions with independent cookies, storage, and tabs. Each named session can be controlled separately and listed with agent-browser session list.

Can agent-browser run on mobile or iOS simulators?

Yes, it supports iOS Simulator via the -p ios flag with Appium and Xcode on macOS. It also supports device emulation with set device for viewport and user agent spoofing on desktop Chrome.

Why do element refs stop working after clicking a button?

Refs are invalidated whenever the page changes, including navigation, form submissions, and dynamic content updates. Always run snapshot -i again after such actions to obtain fresh refs before interacting further.

How do I restrict agent-browser to trusted domains?

Set AGENT_BROWSER_ALLOWED_DOMAINS to a comma-separated allowlist, which blocks navigation and sub-resource requests to other domains. You can also use an action policy file to gate destructive actions and content boundaries to mark untrusted page output.