browser-use

Operate the agent-browser CLI for interactive pages, forms, and multi-account browser sessions.

154|27|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/openvetta/open-vetta --skill browser-use-openvetta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-use
Source: https://github.com/openvetta/open-vetta/tree/main/packages/plugins/presets/browser/agent/skills/browser-use
Command: npx skills add https://github.com/openvetta/open-vetta --skill browser-use-openvetta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser.

What problem does it solve? Automating real browser interactions—logging in, clicking elements, filling forms, and reading rendered pages—requires a controlled browser with persistent session state, which plain HTTP requests or web search cannot provide. ## Core Features & Use Cases - Managed Runtime Bootstrap: Verifies and installs the pinned agent-browser CLI (0.34.0+) and Chrome for Testing through a Vetta-managed npm prefix without touching the user's system installation. - Session-Scoped Automation: Runs every browser command under the task's VETTA_AGENT_SESSION_ID with --pin-tab, so concurrent agent tasks never share or hijack browser state. - Interactive Page Control: Uses snapshot refs (@e1) with click, fill, type, select, wait, and batch commands to drive dynamic pages, with account isolation via session key suffixes and --restore for persistent logins. - Use Case: Ask the agent to log into a dashboard, navigate to a report page, fill a filter form, and extract the resulting table text—all within an isolated, reviewable browser session. ## Quick Start Ask the agent to open a website in a real browser, fill in the login form, and read the resulting page content.

Frequently Asked Questions about browser-use

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

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

Run agent-browser with your session ID to open a page, then use snapshot -i -c to get interactive element refs like @e1. Pass those refs to click, fill, type, or select commands, and re-snapshot after any navigation or page change.

How do I manage multiple accounts in one browser automation task?▼

Append a stable account key to the session ID, such as <session>-youtube-brand-a, to isolate each account. Use --restore <account-key> to persist cookies and local storage across independent agent sessions, with a unique key per account.

What version of agent-browser does Vetta require?▼

Vetta requires agent-browser 0.34.0 or newer. If the CLI is missing or outdated, it is installed with npm install --global agent-browser@0.34.0 using the Vetta-managed npm prefix, never the user's system npm installation.

Why do my browser element refs stop working after clicking?▼

Refs become stale whenever the page navigates, submits a form, or re-renders dynamic content. Run snapshot -i -c again after any state change and use the fresh refs instead of reusing old ones.

When should I use web search instead of browser automation?▼

Use web search for ordinary public information lookup, since it is faster and needs no browser. Reserve the agent-browser CLI for tasks requiring login state, form interaction, or rendered page content that search cannot access.