vc-agent-browser

Automates browser interactions via CLI using context-efficient accessibility snapshots with element refs.

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-agent-browser-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-agent-browser
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-agent-browser
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-agent-browser-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Browser automation for AI agents typically floods the context window with massive DOM dumps or accessibility trees, making long autonomous sessions expensive and slow. This Skill provides a CLI that uses a snapshot-plus-refs paradigm, reducing context usage by roughly 93% compared to Playwright MCP while supporting full browser control. ## Core Features & Use Cases - Snapshot + Refs Workflow: Capture interactive elements as compact refs (@e1, @e2) and interact with them via click, fill, type, and drag commands. - Session & State Management: Save and reload authenticated browser state, manage cookies and storage, and run named parallel sessions. - Recording & Cloud Browsers: Record session videos, export PDFs, and run on Browserbase cloud browsers for CI/CD pipelines. - Use Case: An AI agent needs to log into a web app, fill a multi-step form, and verify the result. It runs agent-browser open, takes a compact snapshot, fills fields by ref, and waits for the dashboard URL—all within a few hundred tokens of context. ## Quick Start Ask the agent to open a URL with agent-browser, take an interactive snapshot, and click or fill elements using the returned refs.

Frequently Asked Questions about vc-agent-browser

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

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

Follow the four-step pattern: run agent-browser open with a URL, run agent-browser snapshot -i to get interactive elements with refs, interact using commands like click @e1 or fill @e2, then re-snapshot after page changes.

What is the difference between agent-browser and chrome-devtools?

agent-browser is a Rust-based CLI using Playwright, best for long autonomous sessions, video recording, and Browserbase cloud browsers. chrome-devtools uses Puppeteer scripts and offers screenshot auto-compression, WebSocket full-frame debugging, and fine-grained console filtering.

How do I use Browserbase cloud browsers with agent-browser?

Set the BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID environment variables, then pass -p browserbase to any command, for example agent-browser -p browserbase open https://example.com. Sessions are created on open and terminated on close.

How do I persist login state across browser automation sessions?

After logging in, run agent-browser state save auth.json to store cookies and storage. In later sessions, run agent-browser state load auth.json before navigating to restore the authenticated state.

Why does agent-browser report element not found errors?

Element refs become stale after the page changes or navigates. Re-run agent-browser snapshot -i to get fresh refs, and verify the element exists in the new snapshot before interacting with it.

Can agent-browser run parallel browser sessions?

Yes, use the --session flag with a unique name per session, such as agent-browser --session test1 open URL in one terminal and --session test2 in another. Each named session maintains an isolated browser instance.