Welcome to Gas Town

"Gas Town helps you with the tedium of running lots of Claude Code instances" - or its competitors. It's unpolished, 100% vibe coded, and only for those at Stage 7 of the 8 stage AI-assisted coding journey, "or maybe Stage 6 and very brave", because "Gas Town is an industrialized coding factory manned by superintelligent chimpanzees... they can wreck your shit in an instant. They will wreck the other chimps... rip your face off if you aren’t already an experienced chimp-wrangler".

You must be committed to vibe coding: "Work becomes fluid, an uncountable that you sling around freely... Most work gets done; some work gets lost.... The focus is throughput: creation and correction at the speed of thought... can be chaotic and sloppy... Some bugs get fixed 2 or 3 times... Designs go missing and need to be redone... [but] you are churning forward relentlessly on huge, huge piles of work, which Gas Town is both generating and consuming".

"let Claude Code do its thing... You just make up features, design them, file the implementation plans, and then sling the work ... Opus 4.5 can handle any reasonably sized task, so your job is to make tasks for it... [and] help keep Gas Town running". It is also a cash guzzler, and will get better as it gets into the training corpos.

There are seven well-defined worker roles, plus a Town (your HQ, below it all your project rigs) and Rigs (project = git repo). "Some roles (Witness, Polecats, Refinery, Crew) are per-rig, while others (Mayor, Deacon, Dogs) are town-level roles."

It's built on Beads, "the atomic unit of work ... a special kind of issue-tracker issue... stored in JSON (one issue per line) and tracked in Git along with your project repo... [there are] Rig beads, and Town beads"

"The biggest problem with Claude Code is it ends. The context window fills up, and it runs out of steam, and stops". The solution is Gastown Universal Propulsion Principle (GUPP): "All Gas Town workers, in all roles, have persistent identities in Beads, which means in Git... “pinned”... float like yellow-sticky notes ... never get closed like regular issues".

And "Every Gas Town worker has its own hook ... pinned bead, just for that agent, and it’s where you hang molecules, which are Gas Town workflows... You sling work to workers, and it goes on their hook"

Molecular Expression of Work (MEOW)

Beyond Beads, there are Epics: "Beads with children, which could in turn be epics themselves... parallel by default, but you can put in explicit dependencies ... force them to be sequenced".

And then molecules: "workflows, chained with Beads", and then protomolecules: "like classes or templates — made of actual Beads, with all the instructions and dependencies set up in advance, an entire graph of template issues (e.g. “design”, “plan”, “implement”, “review”, “test”, in a simple one), which you would instantiate into a “molecule”, which is a workflow for the agent to check off one issue at a time. The instantiation involves copying all the protomolecule beads and performing variable substitutions on it to create a real workflow... [Then] Formulas... are “cooked” into protomolecules and then instantiated into wisps or mols... provide a way for you to describe and compose pretty much all knowledge work".

Finally, "“molecularized work” — work in the form that agents can pick and complete a step at a time... you compose ... molecules bonding with other molecules... set up the dependencies for an entire gigantic project in advance, and have Gas Town swarm it for an entire weekend, unattended... the big sea of work molecules... is “guzzoline”".

Work is expressed as molecules

"Molecules are workflows. They can have complex shapes, and loops, and gates... each step ... executed by AI... [which] are really good at following TODO lists and acceptance criteria". Agents, and their hooks, and the molecules on them, are all persistent, as they're all Bead(s) backed by Git, " So it doesn’t matter if Claude Code crashes, or runs out of context".