gstack

Drive a persistent Chromium daemon for browser-based QA interactions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables Claude Code to drive a persistent browser for automated QA, enabling tests, recordings, and regression checks without leaving the terminal.

Core Features & Use Cases

  • Persistent browser sessions: maintain cookies, tabs, and state across commands for longer QA flows.
  • Navigate, read, and interact: goto, text, html, click, fill, screenshot, and diff workflows across pages.
  • Batching and diagnostics: execute multiple commands in a single request, annotate results, and compare before/after snapshots to verify changes.

Quick Start

Install the skill, run the setup, then invoke /browse to start a QA session.

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 directly from the terminal?

The skill enforces per-session state, local token-based authentication, and safe command boundaries to secure your browser QA sessions. This ensures that multi-tab navigation, cookie management, and form interactions remain isolated and protected during testing.

How do I run multiple browser automation commands in a single request?

Batching browser commands allows you to execute multiple interactions like goto, click, and fill in a single request. You can then annotate results and compare before and after snapshots to verify changes efficiently.

Can I use Claude Code for Playwright browser automation and regression checks?

Yes, Claude Code can drive a persistent Chromium daemon to perform regression checks and deployment verification. It supports screenshot annotations and diff workflows to compare page states before and after changes.

How do I manage cookies and session state for automated browser testing?

Persistent browser sessions maintain cookies, tabs, and state across multiple commands. This allows you to sustain longer QA flows and manage cookies directly through the CLI during automated testing.