Gas City — SDK for Building Custom Dark Factories¶
Type: Dark factory SDK / orchestration framework
Creators: Julian Knutsen and Chris Sills
Based on: Steve Yegge's Gas Town vision
License: MIT open source
Repo: https://github.com/gastownhall/gascity
Related: steve-yegge-gas-town, steve-yegge-gupp, steve-yegge-hierarchy, steve-yegge-beads, steve-yegge-meow, steve-yegge-wasteland
Overview¶
Gas City is Gas Town torn apart and rewritten from the ground up as an SDK for building your own dark factories. It enables teams of collaborating agents to be deployed in any topology — not just the hardwired Gas Town shape — using composable declarative building blocks called packs.
Released v1.0.0 on April 24, 2026, Gas City is the next step in the Gas Universe progression: Beads → Gas Town → The Wasteland → Gas City.
Yegge's own assessment: "It's exactly what I wished for, and it is being run by far more serious and disciplined engineers than me."
Core Concept: Packs¶
Packs are the fundamental building block in Gas City. A pack is a declarative configuration that defines:
- Agent identities, prompts, and personas
- Sandboxes and isolation boundaries
- Skills and capabilities
- Inter-agent messaging topology
- Hooks and triggers (GUPP-driven)
Packs can be composed, imported, and combined to build arbitrary multi-agent topologies. Gas City ships with a Gas Town pack that runs an exact replica of the original — making it a drop-in replacement.
Gas City vs Gas Town¶
| Gas Town | Gas City | |
|---|---|---|
| Form | Single product | SDK / composable toolkit |
| Agent topology | Hardwired (Mayor → Crew → Polecats) | Arbitrary, declared via packs |
| Maturity | Experiment / Wild West | Enterprise-focused, rapidly maturing |
| Custom factories | Not natively supported | Built in — the core use case |
| Drop-in replacement | N/A | Yes — Gas Town pack ships in box |
| Factory Worker API | No | Yes — for coding agent maintainers |
| Model selection | Fixed | Fine-grained at multiple levels |
| Community | Small | Thousands of active Discord members |
The key shift: Gas Town is a dark factory you use. Gas City is a toolkit for building dark factories.
The Light Factory¶
Gas City is called a Light Factory because it maximizes observability. All agent workers are equally visible and addressable — you can interact with any worker at any time. Nothing is hidden except what you explicitly guardrail.
This differentiates Gas City from coding-agent subagents, which intentionally keep the lights off for simplicity. In Gas City, even ephemeral workers (analogous to Gas Town's "polecats") are addressable.
Gas City is the only dark factory designed with the explicit goal of creating other factories.
MEOW Stack: Beads + Dolt¶
Gas City is backed by the MEOW stack (Molecular Expression of Work):
- Beads — Git-versioned work primitive; every discrete unit of work (task, message, coordination signal) is a Bead
- Dolt — Git-versioned SQL database; the forensic powerhouse underneath
The combination means every action by every agent is logged in a database with full git version history. This makes auditing, forensics, rollback, and replay possible in ways that no other multi-agent framework matches.
Multi-Agent Reliability¶
A core architectural principle: never deploy a single agent for real business processes. Agents can go temporarily insane at any time — hallucinations and false memories are mathematically unavoidable. The solution is crews: 2–3 agents watching each other, catching mistakes, and reaching reliable consensus.
Gas City is designed around this insight. Packs let you define adversarial group structures for teams of collaborating agents. The supervisor plane (Gas City itself) keeps them running even on remote machines.
11 Stages of AI Adoption¶
Gas City maps to Yegge's extended AI adoption ladder:
Stage 1-8 → Original dev AI evolution (IDE → orchestrator mastery)
Stage 9 → First deployed agent pack (24x7 business process; "your garden")
Stage 10 → Multiple packs deployed; human becomes control plane bottleneck
Stage 11 → Factory Builder: build crews to manage subsets of deployed packs
At Stage 11, you're operating as architect, curator, and shepherd — not doing the work yourself.
Factory Worker API¶
The Factory Worker API exposes Gas City's supervisor capabilities to coding agent maintainers. This enables:
- Making your own agent the driver for Gas City
- Deep integration with custom supervisor-plane logic
- Programmatic pack deployment and management
Why It Matters for Factory Builders¶
For anyone building dark factory systems:
- Composability — You're not locked into a single topology. Define your problem space and build the agent shape that fits.
- Drop-in Gas Town compatibility — Existing Gas Town users can migrate trivially; the Gas Town pack is the default startup.
- Unparalleled auditability — Dolt-backed git-versioned logs mean you can replay, audit, and rollback any agent action.
- Light factory design — Full observability is the default; you choose what to hide.
- Open source / MIT — No vendor lock-in; enterprise-ready but fun for tinkerers.
Key Quotes¶
"Gas City has deconstructed the entire Gas Town stack into composable, declarative building blocks called 'packs'. You can use these to assemble arbitrary agent topologies, deploy them, sit back, and watch them work from a rich console."
"Gas City is the supervisor plane that connects, manages, and coordinates these deployed mini-factories."
"Gas City is, as far as I can tell, the only viable solution for building custom orchestrators backed by Git."
Summary¶
Gas City is the SDK that turns the Gas Town vision into a general-purpose dark factory construction toolkit. Built by Julian Knutsen and Chris Sills, MIT-licensed, backed by Beads and Dolt, it provides declarative packs for arbitrary agent topologies, ships with a drop-in Gas Town replica, exposes a Factory Worker API, and is designed as a Light Factory where the lights are always on for operators. It is the recommended path forward for anyone building custom multi-agent orchestration systems.