Gas Town: from Clown Show to v1.0
Where "The Flat Curve Society" was Yegge the skeptic-of-hype, this is Yegge the builder taking a victory lap. It's a release note dressed as an essay: Gas Town survived a chaotic first quarter and reached a stable v1.0, and he uses the milestone to sketch what agent orchestration looks like once it stops crashing.
The milestone
The title is literal. In Gas Town's early weeks the Mayor — the on-screen face you talk to — earned a new clown nose every time the system lost data, and it kept happening. That was the "clown show." The v1.0 announcement is the punchline reversed: after a wild three-month ride (roughly 13k GitHub stars and hundreds of committers, per Yegge — verify before quoting the number), the thing is finally boring in the best way.
"The Mayor scored a new clown nose every time it had massive data loss, which went on for weeks."— Gas Town: from Clown Show to v1.0
"Gas Town 'just works.' It does its job, it has tons of integration points, and it has been stable for many weeks."— Gas Town: from Clown Show to v1.0
The Mayor runs the town
Gas Town's whole metaphor is a town. You talk to the Mayor; the Mayor supervises a crew of AI "worker" agents that do the actual coding. The Mayor's job is to spare you the firehose — instead of reading everything the agents print, you read the Mayor, who has already absorbed it and holds your context. Yegge frames this as a rung up the delegation ladder from a single coding agent.
"The Mayor reads all that crap that the workers are printing. The Mayor knows your context, your hopes and dreams."— Gas Town: from Clown Show to v1.0
"If Claude Code is an Executive Assistant, then the Gas Town Mayor is more like your Chief of Staff, who manages a full team of capable EAs, all working for you behind the scenes."— Gas Town: from Clown Show to v1.0
Beads: the missing "Why"
Shipping alongside Gas Town — and hitting its own v1.0 — is Beads, an external-memory and issue-tracking layer Yegge pitches as the piece your version history never captured. Git tells you what changed; Beads is meant to hold why. It's the durable context store that lets the agents (and you) remember the reasoning behind decisions instead of re-deriving it every session.
"Beads is the Why — the missing piece in your commit history."— Gas Town: from Clown Show to v1.0
Where Yegge says this goes
The forward look is unapologetically bullish. He reports non-technologists already building real software through Gas Town, and predicts that talking to an on-screen face — not typing — becomes the dominant way people program before the year is out. The larger bet is Gas City: the modular platform the town lives inside, which he argues will out-design monolithic single-agent tools.
"Non-technologists using Gas town to build software! It sounds crazy but I'm seeing it all over."— Gas Town: from Clown Show to v1.0
"By the end of 2026, people will be mostly programming by talking to a face."— Gas Town: from Clown Show to v1.0
How to read it
This is a milestone post from the project's own creator, so read the confidence accordingly — the star counts, the "just works," and the end-of-2026 prediction are a builder's case for his own tools, not a neutral audit. What's concrete and checkable is the shape of the bet: orchestration over a single agent, a human-readable Mayor layer sitting on top of raw agent output, and a durable "why" store (Beads) bolted onto version control. Those are the ideas worth carrying whether or not the timeline lands on schedule.