browse

Automate QA flows with a persistent headless Chromium session.

5|Updated Apr 24, 2026

Search Tags:#automation #playwright #browse #headless-browser #qa-testing #bug-reproduction

Ready to run

npx skills add https://github.com/timurgaleev/vibestack --skill browse-timurgaleev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/browse
Command: npx skills add https://github.com/timurgaleev/vibestack --skill browse-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent headless Chromium for QA testing and site dogfooding, with state preserved across calls (cookies, tabs, login sessions) to enable repeatable checks without reloading setup.

Core Features & Use Cases

Persistent headless Chromium with fast command execution (~100ms per command) for rapid QA feedback.
Supports common QA patterns: navigation, interaction, form filling, diffs, and visual verification to capture evidence.
Use cases include verifying deployments, reproducing bugs, and building guided test flows for demos.

Quick Start

Run vibestack's browse tool to start a local session and begin testing by issuing commands like goto <url>, click <sel>, and screenshot <path>.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I maintain a persistent headless browser session for QA testing?▼

Persistent headless browser sessions for QA testing are maintained using a Playwright-based daemon that preserves state, including cookies and login sessions, across multiple calls without reloading setup.

How do I automate end-to-end QA flows with Playwright for bug reproduction?▼

Automate end-to-end QA flows and bug reproduction by issuing rapid commands for site navigation, element interaction, and visual capture, enabling stable test orchestration and evidence gathering.

Can I use a headless browser to verify local deployments without losing my login state?▼

Yes, a headless Chromium daemon preserves your login state and tabs across calls, enabling you to verify local deployments and execute repeatable checks without reloading the environment setup.

What is the best way to capture visual evidence during automated site testing?▼

The best way to capture visual evidence during automated site testing is to use a fast headless browser runtime that supports direct screenshot commands to save visual proof of page states.

Does headless browser automation support cross-call element references for test orchestration?▼

Yes, headless browser automation relies on a daemon to preserve state across calls, enabling cross-call element references and stable test orchestration for complex feature verification workflows.