gstack

Coordinate a persistent headless Chromium browser via a Bun-based server and CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff.

What problem does it solve?

QA teams and AI agents often struggle to automate web interactions reliably, while keeping a stable, auditable browser state. gstack provides a fast, persistent headless browser daemon and a minimal CLI surface to drive it from Claude Code and other agents, enabling deterministic, testable web automation.

Core Features & Use Cases

  • Persistent headless browser daemon powered by Playwright with a Bun-based server and a stable state file, enabling quick replays and session continuity.
  • Deterministic toolset for navigation, interaction, diffing, screenshots, and cookies that supports reproducible bug reproduction and QA workflows.
  • Cross-project dogfooding & QA: integrate into CI-like prompts and agent prompts to validate deployments, triage issues, and collect evidence.
  • Workspace isolation: maintain separate browser contexts per repo/workspace to prevent cross-contamination of sessions or cookies.

Quick Start

Install gstack, then run the browse CLI to start the headless browser for your QA workflow.

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?

Persistent headless browser automation for QA requires a daemon that maintains browser state across sessions. gstack provides a Bun-based server running a persistent headless Chromium via Playwright, enabling quick replays and session continuity for deterministic web automation.

Can I drive Playwright browser interactions from a CLI for AI agents?

You can drive Playwright browser interactions from a CLI for AI agents. gstack exposes a minimal CLI surface that coordinates a long-running headless Chromium browser, allowing Claude Code or other agents to execute navigation, interaction, and screenshot tasks deterministically.

Does gstack support workspace isolation to prevent cross-contamination of browser cookies?

Yes, workspace isolation is supported to prevent cross-contamination of browser cookies. gstack maintains separate browser contexts per repo or workspace, ensuring that sessions and cookies remain isolated during cross-project dogfooding and QA workflows.

What is the best way to reproduce bugs deterministically in web automation?

The best way to reproduce bugs deterministically in web automation is using a persistent browser daemon with a stable state file. gstack ensures deterministic interactions for navigation, diffing, and screenshots, supporting reproducible bug reproduction and reliable QA workflows.

How do I collect evidence and triage issues during cross-project QA validation?

To collect evidence and triage issues during cross-project QA validation, integrate a deterministic browser toolset into CI-like prompts. gstack supports navigation, diffing, screenshots, and cookies to validate deployments and collect evidence across isolated workspace contexts.

Do I need Bun installed to run a Playwright-based browser daemon?

Yes, a Bun-based server is required to run the Playwright-based browser daemon. gstack uses a Bun-based server to coordinate the long-running headless Chromium browser, ensuring fast, persistent interactions and deterministic automation workflows.