skills.rest
fray-cloud
fray-cloudCOMMUNITY
Explore all skills by this author →
GitHub

gstack

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

Updated Mar 23, 2026
Search Tags:#automation#testing#qa#cli#playwright#headless#browse
One-click install
npx skills add https://github.com/fray-cloud/coin --skill gstack-fray-cloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/fray-cloud/coin --skill gstack-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

gstack provides a persistent, CLI-driven browser automation layer that lets AI agents control a headless Chromium for reliable QA testing and bug reproduction.

Core Features & Use Cases

  • Persistent browser daemon: keeps cookies, sessions, and state across commands to enable realistic, multi-step interactions.
  • Browser commands: navigate, read, interact, and export diffs and annotated screenshots to verify changes.
  • Use cases: run end-to-end QA tests on staging pages, capture bug evidence, and dogfood user flows with automated checks.

Quick Start

Run the gstack browse CLI to start the headless browser and begin 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 headless browser QA testing with a persistent session?▼

Automate headless browser QA testing using a persistent Chromium daemon that retains cookies and state across CLI commands, enabling reliable multi-step interactions for modern web apps.

Can I capture annotated screenshots during bug reproduction with a headless browser?▼

Yes, you can capture annotated screenshots during bug reproduction. The browser commands support navigation, content extraction, and visual exports to verify changes and capture bug evidence.

Do I need Bun and Playwright to run the headless Chromium server?▼

Yes, you need Bun and Playwright. The Skill requires a Bun/Playwright-based server alongside a token-authenticated HTTP API to manage the headless Chromium daemon and ensure repeatable browser interactions.

How does a CLI control plane manage browser automation for end-to-end tests?▼

A CLI control plane manages browser automation by sending commands to a persistent headless daemon. This architecture allows you to navigate, read, and interact with staging pages for automated end-to-end checks.

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

The best way to maintain state is using a persistent browser daemon. It keeps sessions and cookies active across multiple commands, ensuring realistic and continuous interactions without resetting the context.

Why use a persistent headless daemon instead of standard browser automation for design reviews?▼

A persistent headless daemon maintains session continuity for design reviews, overcoming standard automation limitations. It allows you to dogfood user flows and export visual diffs across multi-step interactions reliably.

Related Skills

Explore More Software Engineering Skills→
a29paula29paul
1

gstack

Automate website testing and deployment verification with persistent headless browser control.

Community
Advanced
JaykaijackJaykaijack

browse

Automate headless Chromium browsing and UI verification with screenshots and diffs.

Community
Advanced
enbyaugustenbyaugust
30

vercel-e2e-test

Deploy Vercel previews and run Playwright tests against staging.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

gstack

Run a persistent headless Chromium daemon with Playwright under Bun via HTTP.

Community
Advanced