Garry Tan Releases gstack: An Open-Supply Claude Code System for Planning, Code Overview, QA, and Transport

What if AI-assisted coding grew to become extra dependable by separating product planning, engineering overview, 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 expertise backed by a persistent browser runtime. The tookit describes itself as ‘Eight opinionated workflow expertise for Claude Code‘ and teams widespread software program supply duties into distinct modes akin to planning, overview, transport, browser automation, QA testing, and retrospectives. The aim is to not substitute Claude Code with a brand new mannequin layer. It’s to make Claude Code function with extra express function boundaries throughout product planning, engineering overview, launch, and testing.

The 8 Core Instructions

The gstack repository at the moment exposes 8 primary instructions: /plan-ceo-review, /plan-eng-review, /overview, /ship, /browse, /qa, /setup-browser-cookies, and /retro. Every command is mapped to a particular working mode. /plan-ceo-review is positioned as a product-level planning cross. /plan-eng-review is used for structure, knowledge move, failure modes, and checks. /overview is concentrated on manufacturing danger and code overview. /ship is used for making ready a prepared department, syncing with primary, working checks, and opening a PR. /browse provides the agent browser entry, whereas /qa is designed for systematic testing of affected routes and flows. /setup-browser-cookies imports cookies from a neighborhood browser into the headless session, and /retro is used for engineering retrospectives.

The Persistent Browser Is the Core System

A very powerful technical a part of gstack just isn’t the Markdown expertise. It’s the browser subsystem. gstack provides Claude Code a persistent browser and that the browser is the arduous half, whereas the remainder is especially 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 instrument 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 robotically 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 by 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 move within the repo reveals /qa inspecting 8 modified information and 3 affected routes, then testing these routes in opposition to a neighborhood app occasion. This implies the undertaking is making an attempt to tie supply modifications to precise software conduct as an alternative of treating QA as a indifferent guide cross.

Set up Necessities and Venture Format

The repository’s implementation decisions are additionally pretty particular. gstack requires Claude Code, Git, and Bun v1.0+. The bundle.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 move copies the repo into ~/.claude/expertise/gstack, runs ./setup, and registers the abilities for Claude Code. Groups may also copy the identical setup right into a repository-local .claude/expertise/gstack listing so the workflow is shared inside a undertaking.

Why the Venture Makes use of Bun

The structure doc explains why the undertaking makes use of Bun moderately than a extra standard Node.js setup. There are 4 said causes: compiled binaries, native SQLite entry, native TypeScript execution, and a built-in HTTP server with Bun.serve(). These decisions are sensible moderately than beauty. gstack reads Chromium’s SQLite cookie database straight, and Bun’s built-in database help removes the necessity for further native packages. The compiled binary mannequin additionally suits the repo’s set up fashion, as a result of customers are usually not anticipated to handle a separate runtime toolchain inside ~/.claude/expertise/.

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 expertise for planning, overview, transport, browser automation, QA, cookie setup, and retrospectives.
• The persistent browser daemon is the primary technical element. 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 /qa workflow analyzes department diffs, identifies affected routes, and checks the related software paths as an alternative of treating browser checks as a separate guide step.
• The undertaking 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 primary worth is separating product overview, engineering overview, code overview, launch, and browser-driven validation into express modes with slender duties.

Take a look at Repo right here. Additionally, be at liberty to comply with us on Twitter and don’t neglect to hitch 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.