gstack

Automates QA browser tasks via CLI-driven persistent headless Chrome daemon with annotated screenshots and cookie management.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast, repeatable browser automation is hard to reproduce manually. gstack provides a fast, persistent headless browser daemon controlled by a CLI to automate QA testing, site dogfooding, and design reviews.

Core Features & Use Cases

  • Persistent browser daemon accessible via a Bun-based CLI for deterministic navigation, interaction, diffs, annotated screenshots, and seamless session/cookie management.
  • Supports workflows like QA testing, design reviews, ship pipelines, and autoplan by providing a stable surface for goto, click, fill, snapshot, diff, and more.
  • Enables evidence-driven QA with diffs, annotated screenshots, responsive checks, and cross-workspace isolation for parallel testing.

Quick Start

Launch the gstack browser with the browse command, then load your target URL to begin automated QA testing.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate QA testing with a persistent headless browser?

Automate QA testing by driving a persistent headless Chrome daemon via a CLI to navigate, interact, and capture annotated screenshots. This approach ensures reliable page interaction and repeatable browser automation for site dogfooding and design reviews.

What's the best way to capture visual evidence during browser automation?

Capture visual evidence during browser automation by using deterministic primitives to take annotated screenshots and generate diffs. This enables evidence-driven QA by highlighting visual changes and supporting responsive checks for design reviews.

Can I manage browser sessions and cookies for automated site navigation?

Manage browser sessions and cookies for automated site navigation through seamless session and state management provided by the persistent daemon. Cross-workspace isolation further supports parallel testing without state conflicts.

How do I run deployment checks and design reviews in a ship pipeline?

Run deployment checks and design reviews in a ship pipeline by utilizing a stable surface for goto, click, fill, and snapshot actions. The persistent browser daemon provides the deterministic execution needed for reliable deployment verification.

Does headless browser automation require a specific runtime environment?

Headless browser automation via this approach requires a Bun-based binary runtime environment. It relies on a SKILL.md frontmatter to define allowed tools and provides safety features such as idle timeout and token-based auth for secure execution.

Why does my browser automation lack reliability during page interaction?

Browser automation lacks reliability when using ephemeral browser instances that lose state between runs. A persistent headless daemon solves this by maintaining session state and providing deterministic primitives for consistent page interaction and diffing.