browser-usage

Automate browser interactions via the agent-browser CLI using accessibility-tree snapshots and element refs.

9|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Yassimba/loom --skill browser-usage-yassimba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-usage
Source: https://github.com/Yassimba/loom/tree/main/skills/browser-usage
Command: npx skills add https://github.com/Yassimba/loom --skill browser-usage-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? AI agents struggle to operate real web pages because raw HTML is verbose and brittle selectors break easily. This Skill teaches agents to drive Chrome/Chromium through the agent-browser CLI using compact accessibility-tree snapshots with stable @eN refs, so clicking, filling forms, extracting data, and taking screenshots work reliably in a few hundred tokens. ## Core Features & Use Cases - Snapshot-and-act loop: Open a page, run agent-browser snapshot -i to get interactive element refs, then click, fill, select, or upload using those refs, re-snapshotting after every page change. - Session and auth management: Use named sessions, --restore persistence, the auth vault, and credential-provider plugins to log in once and stay logged in across runs without exposing passwords. - Advanced workflows: Mock network requests, record HAR files and videos, run axe-core accessibility audits, inspect React component trees, capture Web Vitals, and manage tabs, iframes, and dialogs. - Use Case: An agent needs to log into a web app, navigate to a dashboard, and extract a table of results. It opens the login page, snapshots the form, fills credentials via the auth vault, waits for the dashboard URL, then extracts the data with get text or eval. ## Quick Start Use the browser-usage skill to open https://example.com, take an interactive snapshot, and click the first link.

Frequently Asked Questions about browser-usage

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

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

Open a page with `agent-browser open <url>`, run `agent-browser snapshot -i` to get interactive element refs like @e1, then act with commands such as `click @e1` or `fill @e2 "text"`. Re-snapshot after any page change because refs go stale.

How do I keep a browser session logged in across runs?

Use a named session with `--restore`, which auto-saves cookies and storage on close and reloads them on the next run. Alternatively, save credentials in the auth vault with `agent-browser auth save` and log in via `agent-browser auth login`.

Does agent-browser require Playwright or Puppeteer?

No, agent-browser drives Chrome or Chromium directly over the Chrome DevTools Protocol with no Playwright or Puppeteer dependency. Install it with `npm i -g agent-browser` followed by `agent-browser install`.

Why does agent-browser report "Ref not found" or "Element not found"?

Refs are assigned fresh on every snapshot and become stale the moment the page changes through navigation, form submits, or dynamic re-renders. Run `agent-browser snapshot -i` again and use the new refs for your next interaction.

Can agent-browser run multiple isolated browser sessions in parallel?

Yes, each `--session <name>` creates an isolated browser with its own cookies, tabs, and refs. When sessions share one Chrome over `--cdp`, add `--pin-tab` so each session stays bound to its own tab.

What are the limitations of agent-browser accessibility audits?

The built-in axe-core audit requires a CDP-based Chromium browser and is not available with Safari or iOS WebDriver sessions. It reports WCAG violations and incomplete checks, but incomplete rules need manual review.