skills.rest
TimHL5
TimHL5COMMUNITY
Explore all skills by this author →
GitHub

gstack

Drive a persistent headless Chromium daemon via CLI for browser automation.

Updated Mar 21, 2026
Search Tags:#automation#e2e#qa#playwright#browser#headless
One-click install
npx skills add https://github.com/TimHL5/carousel --skill gstack-timhl5
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/TimHL5/carousel/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/TimHL5/carousel --skill gstack-timhl5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent, reliable browser automation for AI QA work: gstack provides a fast, persistent headless browser daemon that Claude Code can drive, enabling deterministic browser-based testing and dogfooding.

Core Features & Use Cases

  • Persistent headless browser: a long-lived Chromium daemon that preserves cookies, tabs, and session state across commands for repeatable testing.
  • Browser tooling suite: navigation, content extraction, interactions (click, fill, type, etc.), snapshot with refs, diff, annotate, and dialog handling.
  • Local QA + design dogfooding: verify flows, gather evidence (screenshots, diffs), and produce test artifacts across projects/workspaces.

Quick Start

Run the gstack browser daemon once, then drive it with browse commands to test a page or workflow.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I run persistent headless browser automation for AI QA testing?▼

Persistent headless browser automation uses a long-lived Chromium daemon to preserve cookies and session state across commands, enabling repeatable QA testing and site dogfooding without losing context between interactions.

Does gstack work with Playwright for headless browser testing?▼

Yes, gstack uses a Playwright-backed server to drive a persistent headless Chromium daemon, providing reliable browser automation, content extraction, and interaction testing for multi-workspace projects.

Can I take screenshots and diffs during headless browser testing?▼

Yes, the browser tooling suite supports snapshot with refs, diff, and annotate functions, allowing you to gather visual evidence and produce test artifacts during QA validation workflows.

What is the best way to maintain session state across browser automation commands?▼

Using a persistent headless browser daemon maintains session state, cookies, and tabs across multiple commands, ensuring deterministic browser-based testing without needing to re-authenticate or reload context.

Do I need Bun installed to run the gstack browser daemon?▼

gstack implements a Bun-compiled binary for its Playwright-backed server, so the appropriate Bun runtime environment is required to execute the daemon and drive browser automation commands locally.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

gstack

Automate browser QA with a persistent headless Chromium daemon.

Community
Advanced
mindcockpit-aimindcockpit-ai
11

workspace-monitor

Detect errors, warnings, and anomalies in project logs and build artifacts.

Official
Advanced
JaykaijackJaykaijack

gstack

Automate persistent headless browser testing and QA for Claude Code agents using Bun and Playwright.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

gstack

Automate persistent headless browser QA testing with Playwright and Chromium.

Community
Advanced