Headbox
Write your project's rules once. Claude, Codex, Gemini, Cursor, Copilot and Windsurf all follow the same ones, instead of six files drifting apart. Then watch it work.
▸ Press startThe Stack
Headbox is usually described as a CLI. The CLI is its strongest surface, but the product is four layers: a rules layer that governs the workspace, the CLI that operates it, a Console that gives it a face, and Live, which lets you watch it work. All four ship today. Pick one.
What this gallery is, and how it stays true
Nothing here is hand-transcribed. The terminal frames are generated by executing the real CLI at build time. Command signatures, plugin registry rows, artifact access rules and vendor targets are parsed from the shipped source. If the code changes, the next build changes with it. a hand-copied gallery drifts silently, and this one structurally cannot.
The arcade skin is the site's; the product's look is the product's. Console components are reproduced
inside a .product scope carrying the Console's own tokens verbatim, so a card here looks like the app
rather than like this page. Everything inside a screen is product; the cabinet around it is staging.
Demo data throughout. The Console runs against real conversations and real project names, so nothing here is a screenshot of it. Names, paths and threads are invented; structure and tokens are real.
Stage Select
The eight terminal surfaces you actually land on. Each frame is verbatim stdout, generated by running cli/headbox.js at build time, so
the output on screen cannot drift from the binary. Names and paths inside are demo data.
Where The Code And The Docs Disagree
Rendering the product beside its documentation is an unusually good way to find where the two quietly drifted apart. These turned up. In each case the site shows what the code does, and says so, rather than silently picking a side.
antigravity ✅ compatibility, which the installer does not back.headbox status cannot read the spec version Shipped bugheadbox status
prints the spec version under a label that reads like the product's, and today it prints unknown
because the spec header no longer matches the pattern it reads. Reproduced exactly as shipped in
surface 02: the product's behaviour, not a gallery bug.npx get-headbox init,
but publishing to npm is still an unticked roadmap item. Today you run the CLI from a clone.active, parked and
dismissed are styled. suggested, confirmed and split
render identically. The gallery shows four distinct signal variants, not six. Showing six would invent
three.