skills.rest
Chang-Shih-Yung
Chang-Shih-YungCOMMUNITY
Explore all skills by this author →
GitHub

gstack

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

Updated Mar 25, 2026
Search Tags:#automation#playwright#headless#browse#qa-testing#cookie-management
One-click install
npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill gstack-chang-shih-yung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/Chang-Shih-Yung/auto-learning/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill gstack-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a persistent headless browser daemon to enable reliable QA testing and design dogfooding workflows by maintaining cookies, tabs, and session state across commands.

Core Features & Use Cases

  • Persistent headless browser daemon for deterministic QA runs.
  • State continuity across commands (cookies, tabs) for reliable test flows.
  • HTTP-based command dispatch to drive Playwright-controlled Chromium from AI agents.

Quick Start

Start the gstack browse daemon and begin a QA session immediately.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I keep cookies and login state persistent across headless browser QA commands?▼

Persistent headless browser daemon operations preserve cookies, tabs, and login state across commands for reliable QA testing. State continuity ensures deterministic test flows by maintaining sessions between HTTP-dispatched instructions.

Can AI agents drive Playwright-controlled Chromium for automated QA testing?▼

Automated QA testing can be driven by AI agents using Playwright-controlled Chromium. A daemon process speaks HTTP to the agent, dispatching commands to the headless browser to execute reliable test workflows.

What is the best way to run deterministic QA testing with headless browser automation?▼

Deterministic QA testing requires a persistent headless browser daemon that maintains tabs and session state. State continuity across commands prevents session loss, guaranteeing reliable execution for repeated test runs.

Does this headless browser automation tool require Bun to run Playwright?▼

Headless browser automation requires Bun to run Playwright under the hood. The environment drives a Chromium daemon that handles HTTP-based command dispatch, enabling AI agents to execute QA workflows.

Why do my headless browser cookies reset between separate QA testing commands?▼

Headless browser cookies reset between commands without a persistent daemon. A continuous background process preserves session state, cookies, and tabs across separate HTTP requests to ensure reliable test flows.

How do I start a persistent headless browser daemon for design dogfooding workflows?▼

Starting a persistent headless browser daemon enables design dogfooding workflows by initiating a background process. This daemon maintains state continuity, allowing immediate and reliable QA session execution.

Related Skills

Explore More Software Engineering Skills→
a29paula29paul
1

gstack

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

Community
Advanced
JaykaijackJaykaijack

gstack

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

Community
Advanced
coalesce-labscoalesce-labs
20

agent-browser

Automate browser navigation, form filling, and UI testing with persisted sessions.

Official
Advanced
rmarino550rmarino550

setup-browser-cookies

Import browser cookies into Playwright headless sessions for authenticated QA testing.

Community
Intermediate