agent-browser

Automates browser interactions to test web UIs, fill forms, and capture screenshots.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/Thigh-Food/emdash --skill agent-browser-thigh-food
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/Thigh-Food/emdash/tree/main/skills/agent-browser
Command: npx skills add https://github.com/Thigh-Food/emdash --skill agent-browser-thigh-food

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying frontend changes and testing web UI interactions manually is slow and repetitive. This Skill gives an AI agent direct control of a browser through a CLI, so it can open pages, inspect the accessibility tree, interact with elements, and capture screenshots without human intervention. ## Core Features & Use Cases - Snapshot-Based Interaction: Generate an accessibility tree with element refs (@e1, @e2) and use them to click, fill, type, select, and check elements deterministically. - Screenshots & Inspection: Capture viewport or full-page screenshots, read text/HTML/values from elements, and check visibility, enabled, or checked states. - Sessions & Debugging: Persist cookies and storage across commands with named sessions, view console logs and page errors, and run headed mode for visual debugging. - Use Case: After modifying a form in your Astro/Cloudflare CMS admin panel, open the page, snapshot the interactive elements, fill the title and content fields, click save, and screenshot the result to confirm the change works. ## Quick Start Use the agent-browser skill to open http://localhost:4321, take an interactive snapshot, and verify the page renders correctly.

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 testing with an AI agent?▼

Use the agent-browser CLI to open a URL, run snapshot with the -i flag to get interactive element refs, then interact using commands like click, fill, and type with those refs. Finish with a screenshot to verify the result visually.

How do I fill and submit a web form from the command line?▼

Open the page with agent-browser open, take an interactive snapshot to find field refs, then use fill @ref "value" for each input and click the submit button ref. Use find label or find placeholder to target fields without refs.

Can browser sessions persist login state between commands?▼

Yes, named sessions keep cookies and storage between commands. Pass --session mytest to each command or set the AGENT_BROWSER_SESSION environment variable to reuse authenticated state across interactions.

Why is my browser automation clicking the wrong element?▼

Element refs change between snapshots, so always take a fresh snapshot before interacting. Use the -i flag for cleaner interactive-only output, or use find role/label commands to target elements by accessible name instead of refs.

How do I debug browser automation that is not working?▼

Run with --headed to watch the browser visually, then use agent-browser console and agent-browser errors to inspect logs and page errors. You can also highlight an element or run eval with JavaScript to inspect page state.