“I've been using gstack for the last few days, and will probably keep it in my skill toolkit... The approach to using the browser is superior to Claude's built-in extension in pretty much every way (except cookie management). It's worth it for that alone. — madrox (https://news.y...”
You know that feeling when you ask an AI coding agent to build something and it hallucinates a plan, skips the review step, and ships broken code? Your agent has no structured workflow — it jumps from idea to code with no plan review, no QA, and no reflection on what went wrong. You end up hand-holding the AI through each phase, re-prompting it to test in a browser, and manually checking its work because there's no pipeline enforcing discipline.
Think of gstack as a pre-built team of specialists you drop into your AI coding agent. You install 23 Markdown skill files that Claude Code discovers as slash-commands (`/office-hours`, `/plan-ceo-review`, `/build`, `/review`, `/qa`, `/ship`). The clever part is a persistent Chromium browser daemon — a Bun-compiled TypeScript binary (~58MB) that stays running in the background. When a skill needs to check a webpage, it sends a command to localhost, which drives Chromium via Playwright's accessibility-tree locators (not DOM injection). First call takes ~3 seconds (cold start), subsequent calls ~100-200ms. Each skill's output feeds into the next in a structured pipeline: you describe an idea in `/office-hours`, get a CEO-level plan review, hand off to engineering, run browser-based QA, then ship.
If you're a developer already using Claude Code (or another AI coding agent) who wants structured workflow discipline and browser-based QA without switching tools. Not useful if you're on Windows and need cookie features, or if your team needs multi-user collaboration (single-user architecture only). Also not for you if you're sensitive to token costs — the full pipeline loads substantial SKILL.md context into each call.
Worth a look if you already use Claude Code and want browser-based QA — that's the feature actual users praise most. Install it, try `/office-hours` on a real project, and see if the pipeline discipline sticks. Know what you're signing up for: this is beta software shipping at extreme velocity (multiple versions per day) with no formal releases, macOS-only cookie decryption, and significant token costs on the planning skills. The 72K stars reflect Tan's platform, not necessarily production maturity.
Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.