What if AI-assisted coding turned extra dependable by separating product planning, engineering evaluation, launch, and QA into distinct working modes? That’s the concept behind Garry Tan’s gstack, an open-source toolkit that packages Claude Code into 8 opinionated workflow abilities backed by a persistent browser runtime. The tookit describes itself as ‘Eight opinionated workflow abilities for Claude Code‘ and teams widespread software program supply duties into distinct modes similar to planning, evaluation, delivery, browser automation, QA testing, and retrospectives. The aim is to not exchange Claude Code with a brand new mannequin layer. It’s to make Claude Code function with extra specific position boundaries throughout product planning, engineering evaluation, launch, and testing.
The 8 Core Instructions
The gstack repository at present exposes 8 fundamental instructions: /plan-ceo-review, /plan-eng-review, /evaluation, /ship, /browse, /qa, /setup-browser-cookies, and /retro. Every command is mapped to a selected working mode. /plan-ceo-review is positioned as a product-level planning cross. /plan-eng-review is used for structure, knowledge movement, failure modes, and checks. /evaluation is concentrated on manufacturing danger and code evaluation. /ship is used for getting ready a prepared department, syncing with fundamental, operating checks, and opening a PR. /browse offers the agent browser entry, whereas /qa is designed for systematic testing of affected routes and flows. /setup-browser-cookies imports cookies from an area browser into the headless session, and /retro is used for engineering retrospectives.
The Persistent Browser Is the Core System
Crucial technical a part of gstack will not be the Markdown abilities. It’s the browser subsystem. gstack offers Claude Code a persistent browser and that the browser is the arduous half, whereas the remaining is principally Markdown. As an alternative of launching a contemporary browser for each motion, gstack runs a long-lived headless Chromium daemon and communicates with it over localhost HTTP. The reason being latency and state retention. A chilly begin prices round 3–5 seconds per software name, whereas subsequent calls after startup are designed to run in roughly 100–200 ms. As a result of the browser stays alive, cookies, tabs, localStorage, and login state persist throughout instructions. The server additionally shuts down routinely after half-hour of idle time.
How gstack Connects Browser Automation to QA
That daemon structure issues for QA and browser-driven improvement. In lots of agent workflows, browser automation is a separate debugging step or a screenshot utility. In gstack, browser entry is a part of the core workflow. The repo describes /browse because the mode that lets the agent log in, click on via the app, take screenshots, and examine breakage. /qa builds on high of that by analyzing the department diff, figuring out affected routes, and testing the related pages or flows. The pattern movement within the repo reveals /qa inspecting 8 modified information and 3 affected routes, then testing these routes in opposition to an area app occasion. This implies the venture is attempting to tie supply modifications to precise software habits as a substitute of treating QA as a indifferent guide cross.
Set up Necessities and Mission Structure
The repository’s implementation decisions are additionally pretty particular. gstack requires Claude Code, Git, and Bun v1.0+. The package deal.json reveals the present model as 0.3.3, lists Playwright and diff as runtime dependencies, and compiles a browse executable from the browse supply tree. In line with the repo’s README, /browse compiles a local binary and is supported on macOS and Linux, for each x64 and arm64. The set up movement copies the repo into ~/.claude/abilities/gstack, runs ./setup, and registers the abilities for Claude Code. Groups can even copy the identical setup right into a repository-local .claude/abilities/gstack listing so the workflow is shared inside a venture.
Why the Mission Makes use of Bun
The structure doc explains why the venture makes use of Bun quite than a extra typical Node.js setup. There are 4 acknowledged causes: compiled binaries, native SQLite entry, native TypeScript execution, and a built-in HTTP server with Bun.serve(). These decisions are sensible quite than beauty. gstack reads Chromium’s SQLite cookie database straight, and Bun’s built-in database assist removes the necessity for further native packages. The compiled binary mannequin additionally matches the repo’s set up model, as a result of customers will not be anticipated to handle a separate runtime toolchain inside ~/.claude/abilities/.
Key Takeaways
- gstack is a workflow layer for Claude Code, not a brand new mannequin or agent framework. It packages software program supply into 8 opinionated slash-command abilities for planning, evaluation, delivery, browser automation, QA, cookie setup, and retrospectives.
- The persistent browser daemon is the primary technical part. gstack runs a long-lived headless Chromium course of over localhost HTTP so cookies, tabs,
localStorage, and login state persist throughout instructions. - QA is tied on to code modifications. The
/qaworkflow analyzes department diffs, identifies affected routes, and checks the related software paths as a substitute of treating browser checks as a separate guide step. - The venture is constructed round Bun for sensible methods causes. Bun is used for compiled binaries, native SQLite entry, native TypeScript execution, and a built-in HTTP server for the browser daemon.
- gstack’s contribution is operational construction. Its fundamental worth is separating product evaluation, engineering evaluation, code evaluation, launch, and browser-driven validation into specific modes with slim duties.
Try Repo right here. Additionally, be at liberty to observe us on Twitter and don’t overlook to affix our 120k+ ML SubReddit and Subscribe to our E-newsletter. Wait! are you on telegram? now you’ll be able to be a part of us on telegram as nicely.
