gstack

Drive a persistent Playwright browser daemon for QA testing.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chriswestt/claude-skills --skill gstack-chriswestt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/chriswestt/claude-skills/tree/main/gstack
Command: npx skills add https://github.com/chriswestt/claude-skills --skill gstack-chriswestt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code often needs a reliable, persistent browser to test pages, run interactions, and gather verifiable evidence. gstack provides a Playwright-based daemon that keeps state (cookies, tabs) and exposes a focused command surface for QA workflows, enabling repeatable testing cycles without reloading or re-authenticating.

Core Features & Use Cases

  • Persistent browser session: maintain cookies and tabs across commands to speed up QA flows.
  • Snapshot, diff, and annotation: capture accessibility refs, compare before/after states, and annotate screenshots for precise validation.
  • Batchful testing: execute multiple commands in a single batch to reduce round-trips and improve throughput during automated testing.
  • Use Case: when validating a staging deployment, run a sequence of navigations, form interactions, and verifications, then generate diffs and annotated evidence for the PR.

Quick Start

Start a QA session by launching the browse client and issuing commands to drive the browser.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I maintain cookies and browser tabs across multiple QA testing commands?

You can maintain cookies and tabs across QA testing commands by using a persistent Playwright-based browser daemon. gstack keeps state active across commands to speed up repeatable testing workflows without reloading or re-authenticating.

Can I capture and diff browser screenshots for staging deployment validation?

Yes, you can capture and diff browser screenshots for staging validation. gstack supports snapshot, diff, and annotated screenshots, allowing you to compare before and after states to generate verifiable evidence for your PRs.

How do I execute batch browser commands to reduce round-trips during automated testing?

You can execute batch browser commands to reduce round-trips by issuing multiple instructions in a single batch. gstack supports batchful testing to improve throughput and speed up automated QA cycles.

Does Claude Code support driving a headless browser for web dogfooding and QA?

Yes, Claude Code supports driving a headless browser for web dogfooding and QA. gstack provides a persistent Playwright-based daemon that Claude Code can drive to run interactions, test pages, and gather verifiable evidence.

What are the safety and isolation limitations when running local browser automation?

The tool emphasizes safety through per-session isolation and ensures local state never leaves the machine. This approach protects your local environment while maintaining persistent browser sessions for automated testing.

Do I need Playwright installed to run automated browser interactions and accessibility snapshots?

Yes, Playwright is the underlying engine for this tool. gstack provides a persistent Playwright-based daemon to run automated browser interactions, capture accessibility refs, and generate snapshots for precise validation.