vc-agent-browser

Automate long-running browser tasks via CLI with named sessions and ARIA snapshots.

1.1k|223|Updated May 27, 2026
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-agent-browser-withkynam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-agent-browser
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-agent-browser
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-agent-browser-withkynam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires debug, puppeteer, sharp, yargs, and includes scripts (resource) and references (resource) components.

What problem does it solve?

AI-driven browser automation for long-running tasks enables AI agents to manage persistent web sessions with context-efficient snapshots, self-healing loops, and cloud-browser testing capabilities.

Core Features & Use Cases

  • Context-efficient snapshots and refs to minimize context switching during long autonomous runs.
  • CLI-driven browser automation for navigation, interaction, and verification across diverse stacks.
  • Cloud/browser testing readiness with support for named sessions and Browserbase integration in CI/CD workflows.

Quick Start

Install the vc-agent-browser tool and run it to initiate an autonomous browser session that can execute a planned sequence without manual intervention.

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 long-running browser sessions for AI agents?

Long-running browser automation for AI agents is managed via a CLI that maintains persistent web sessions, using context-efficient snapshots and self-healing loops to execute planned sequences without manual intervention.

Does Puppeteer work with cloud-browser testing in CI/CD workflows?

Yes, Puppeteer supports cloud-browser testing in CI/CD workflows through Browserbase integration, enabling named sessions and scriptable interactions for autonomous verification across diverse stacks.

What is the best way to minimize context switching during autonomous browser runs?

To minimize context switching during autonomous runs, use ARIA-based snapshots and a pluggable references architecture, which provide context-efficient refs that reduce the need for full-page processing.

Can I run browser automation scripts with named sessions for self-healing loops?

Yes, you can run browser automation scripts with named sessions to support self-healing loops, enforcing safe interactions and maintaining state across persistent tasks during execution.

Why does browser automation fail during long autonomous web tasks?

Browser automation often fails during long tasks due to context overload and state loss, which this tool mitigates using ARIA-based snapshots, self-healing loops, and persistent named sessions.

Do I need Node.js to run CLI-driven Puppeteer browser automation?

Yes, you need Node.js to run this CLI-driven Puppeteer browser automation, as it relies on JavaScript dependencies like sharp and yargs to execute scripts and process interactions.