gstack

Provision a persistent headless Chromium daemon for deterministic browser interactions.

Updated Aug 23, 2026

Search Tags:#automation #qa #playwright #browser #ref #gstack

Ready to run

npx skills add https://github.com/effiraid/reflix-nextjs --skill gstack-effiraid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/effiraid/reflix-nextjs/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/effiraid/reflix-nextjs --skill gstack-effiraid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a persistent headless browser daemon that AI agents can reuse across commands, eliminating flaky tests and flaky browser startups by offering a stable, sharable browser context for QA and dogfooding work.

Core Features & Use Cases

Persistent, deterministic browser session for AI-driven QA and design exploration.
Ref-based element discovery with snapshot diffs and annotated screenshots for evidence.
End-to-end testing support: navigation, interaction, data capture, and reporting across sites.

Quick Start

Start the browse daemon with the CLI, then run QA commands against your site.

Frequently Asked Questions about gstack

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

FAQPage Schema

How do I automate browser QA testing for AI agents?▼

Browser QA testing for AI agents uses a persistent headless Chromium daemon that maintains state across commands, enabling deterministic navigation, interactions, and annotated evidence. This eliminates flaky browser startups.

What is ref-based element targeting in browser automation?▼

Ref-based element targeting in browser automation is a scriptable interface that identifies elements using stable references rather than brittle selectors. It supports snapshotting and logging for reproducible QA workflows.

Can I use a persistent headless browser for product dogfooding workflows?▼

A persistent headless browser supports product dogfooding by maintaining a stable, sharable browser context across commands. It enables end-to-end navigation, interaction, data capture, and reporting across sites.

How do I start a headless browser daemon for QA automation?▼

Start the headless browser daemon for QA automation using the CLI to provision a persistent Chromium instance. Then run QA commands against your site for deterministic navigation and annotated screenshots.

Why are my browser automation tests flaky and how do I fix it?▼

Browser automation tests are flaky due to inconsistent startups and lost state. Fix this by using a persistent headless Chromium daemon that maintains a stable, sharable browser context across all commands.