Key takeaways
- From Steve Yegge, former Google/Amazon engineer — orchestrates 20-30 coding agents (Claude Code, Copilot, Codex, Gemini) simultaneously
- Hit v1.0 in April 2026 and v1.2.1 in June 2026 — moved from Yegge's personal account to the gastownhall org, 15.9K stars
- Kilo now offers a hosted cloud version (GA May 2026), and the Wasteland project federates multiple Gas Towns into a shared network
FAQ
What is Gastown?
Gastown is a multi-agent orchestrator that lets developers run 20-30 coding agents (Claude Code, GitHub Copilot, Codex, Gemini) in parallel using tmux and git-backed work tracking.
Who created Gastown?
Steve Yegge, former senior engineer at Google and Amazon, created Gastown as his fourth attempt at an agent orchestrator in 2025. It now lives in the gastownhall GitHub org, and Kilo offers a hosted version.
What is the relationship between Gastown and Beads?
Gastown is built on top of Beads, Yegge's git-backed issue-tracking and agent-memory system (24K+ GitHub stars), which serves as the control and data plane.
Is Gastown production ready?
It reached v1.0 in April 2026 and v1.2.1 in June 2026, but it remains a chaotic, expert-oriented "vibe coded" system rather than a polished enterprise product.
Executive Summary
Gastown is Steve Yegge's multi-agent orchestrator for running 20-30 coding agent instances in parallel — Claude Code, GitHub Copilot, Codex, Gemini, and others.[1][2] Built on his Beads data system, it uses tmux as its primary UI and implements specialized worker roles (Mayor, Polecats, Refinery, Witness, Deacon, Dogs, and the human Overseer). Since launch it has moved from Yegge's personal account to the gastownhall org, shipped v1.0 (April 2026) through v1.2.1 (June 2026),[3] and gained a hosted cloud version from Kilo.[4] It remains explicitly for expert users comfortable with "vibe coding" at industrial scale.
| Attribute | Value |
|---|---|
| Creator | Steve Yegge |
| Type | Open Source (MIT, gastownhall org) + hosted version by Kilo |
| GitHub Stars | 15.9K (as of June 2026)[2] |
| Language | Go |
| Headquarters | N/A (Independent; Kilo hosts the cloud version) |
Product Overview
Gastown is an opinionated multi-agent orchestrator that Yegge describes as "Kubernetes for agents."[1] It's his fourth complete orchestrator of 2025, representing lessons learned from three failed predecessors. The system manages parallel coding agents — no longer just Claude Code, but also GitHub Copilot, Codex, and Gemini — through a tmux-based interface with specialized worker roles.[2]
The tool solves a specific problem: when running many AI coding agents simultaneously, work gets lost, agents conflict over git operations, and coordination becomes chaotic. Gastown provides structure through its "Town" and "Rig" abstractions.
What Changed Since Launch (as of June 2026)
- v1.0 shipped April 3, 2026; the project is now on v1.2.1 (June 6, 2026) with steady releases[3]
- Repo moved from steveyegge/gastown to the gastownhall GitHub org (MIT license)[2]
- Gas Town by Kilo — a hosted cloud version went GA on May 19, 2026, removing tmux and self-hosting overhead[4]
- The Wasteland (March 2026) — a federated network linking "a thousand Gas Towns" with a shared "Wanted Board" for tasks[5]
- Gas City (April 2026) — Yegge's broader framework for building custom orchestration hierarchies around long-running AI workers[6]
- New primitives — Convoys (bundled work units), Molecules (workflow templates), Hooks (git-worktree persistent storage), and a Bors-style bisecting merge queue in the Refinery[2]
Key Capabilities
| Capability | Description |
|---|---|
| Multi-Agent Parallel Execution | Run 20-30 agent instances (Claude Code, Copilot, Codex, Gemini) simultaneously |
| Seven Worker Roles | Mayor, Polecats, Refinery, Witness, Deacon, Dogs, Overseer |
| Merge Queue | Intelligent conflict resolution via the Refinery role |
| Git-Backed State | All state stored in git via Beads library |
| Tmux UI | Terminal multiplexer as primary interface |
Worker Roles
| Role | Description |
|---|---|
| Mayor | Main agent, concierge and chief-of-staff |
| Polecats | Ephemeral workers that swarm on tasks, produce Merge Requests |
| Refinery | Handles Merge Queue, intelligently combines changes |
| Witness | Watches polecats, helps them get unstuck |
| Deacon | Daemon beacon for system coordination |
| Dogs | Town-level monitoring and alerting |
| Overseer | You, the human operator |
Technical Architecture
Gastown is built on two key components:[2]
- Beads — Yegge's git-backed issue-tracking and agent-memory system, now repositioned as "a memory upgrade for your coding agent" with 24K+ stars; The New Stack reports the backend has migrated to Dolt, a git-style database[7][5]
- Tmux — Terminal multiplexer serving as the primary UI (the Kilo-hosted version removes the tmux requirement)[4]
Core Concepts
| Concept | Description |
|---|---|
| Town | Your HQ directory (e.g., ~/gt) managing all rigs |
| Rig | A single project/repo under Gastown management |
| MR (Merge Request) | Work unit produced by polecats |
| MQ (Merge Queue) | Ordered queue of MRs awaiting integration |
Key Technical Details
| Aspect | Detail |
|---|---|
| Deployment | Local (CLI + tmux) or hosted via Gas Town by Kilo[4] |
| Model(s) | Claude Code, GitHub Copilot, Codex, Gemini, and compatible CLIs |
| Dependencies | Beads, tmux, Go runtime |
| Open Source | Yes (MIT, GitHub) |
Degradation model: Gastown degrades gracefully — every worker can operate independently, and you can run partial configurations or even "no-tmux" mode.
Strengths
- Scale — Enables 20-30 parallel agent instances, far beyond manual management
- Intelligent merging — Refinery role handles the complex "monkey knife fight" of parallel git operations
- Graceful degradation — Works in partial configurations, doesn't require full orchestration
- Expert pedigree — Built by Steve Yegge with decades of Google/Amazon engineering experience
- Open exploration — Tackles the MAKER benchmark problem (20-disc Hanoi towers) that defeats other approaches[8]
- Built on proven foundation — Beads has 24K+ GitHub stars and an active ecosystem[7]
- Sustained momentum — v1.0 through v1.2.1 shipped between April and June 2026, with a hosted option now available[3][4]
Cautions
- "100% vibe coded" origins — Launched on a codebase under 3 weeks old; v1.x has matured it, but the chaotic philosophy persists
- Expert-only — Requires Stage 7-8 on Yegge's AI coding evolution scale
- High cost — Multiple agent subscriptions needed; "cash guzzler"
- Tmux required for self-hosting — Must learn tmux (the Kilo-hosted version removes this)[4]
- Beads lock-in — No alternative backend; must adopt Yegge's full stack
- Chaotic by design — "Work can be chaotic and sloppy" — bugs get fixed multiple times, designs go missing
- Polarizing reception — Hacker News discussion remains sharply divided on whether the token spend produces commensurate value[9]
What Developers Say
Hacker News discussion of Gas Town is unusually polarized:[9]
"It's clear that this is a big fun experiment. It pushes and crosses boundaries, it is a mixture of technology and art." — mediaman
"It reads like the ramblings of a smart person experiencing a psychotic episode." — q3k
"Something that's burning through thousands of dollars, producing what exactly?, is deserving of our respect why?" — PKop
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Gastown (self-hosted) | Free | Open source (MIT) |
| Claude Code / agent CLIs | $20-100/mo each | Required per agent account |
| Gas Town by Kilo | Via Kilo Cloud | Managed hosting, no tmux, 500+ models through Kilo Gateway[4] |
True cost: Yegge mentions needing multiple Claude Code accounts and expecting to need a third within a week of launch. Heavy users should budget $100-300+/month in agent subscriptions or token spend.
Licensing model: Open source (MIT), with a commercial hosted option from Kilo[4]
Competitive Positioning
Direct Competitors
| Competitor | Differentiation |
|---|---|
| Ralph | Ralph is simpler (bash loop); Gastown is full orchestration system |
| Tembo | Tembo is commercial with enterprise features; Gastown is experimental/personal |
| Manual tmux | Gastown adds structure, roles, and merge queue to raw tmux management |
When to Choose Gastown Over Alternatives
- Choose Gastown when: You're already at Stage 7-8 of AI coding evolution, comfortable with chaos, and want to push the boundaries of parallel agent execution
- Choose Ralph when: You want the simplest possible approach (bash loop) without the orchestration complexity
- Choose Tembo when: You need enterprise features, team support, and stability
Ideal Customer Profile
Best fit:
- Expert developers already managing 3-5+ parallel Claude Code instances
- Engineers comfortable with tmux and terminal-first workflows
- Researchers exploring multi-agent coordination
- Developers willing to accept chaos and instability for throughput
Poor fit:
- Anyone not already at Stage 6+ of AI coding adoption
- Teams needing stability and reliability
- Developers uncomfortable with vibe coding philosophy
- Organizations requiring enterprise support or compliance
Viability Assessment
| Factor | Assessment |
|---|---|
| Financial Health | N/A — Open source project; Kilo funds the hosted offering |
| Market Position | Pioneer — Pushing boundaries of multi-agent orchestration |
| Innovation Pace | Rapid — v1.0 to v1.2.1 in three months, plus Wasteland and Gas City spin-offs[3][6] |
| Community/Ecosystem | Growing — 15.9K stars (up from 9.3K in February 2026), Beads at 24K+[2][7] |
| Long-term Outlook | Improved — Kilo partnership and org-owned repo reduce single-maintainer risk, though it still tracks Yegge's attention |
Gastown has moved from raw experiment to a versioned, org-maintained project with a commercial host. Yegge remains highly active — the Wasteland (March 2026), Gas City (April 2026), and the Kilo GA (May 2026) all shipped within this profile's refresh window.[5][6][4] It still embraces chaos by design, and for the right expert users it demonstrates what's possible.
Bottom Line
Gastown is the most ambitious open-source multi-agent orchestrator available, enabling 20-30 parallel agent instances (Claude Code, Copilot, Codex, Gemini) with sophisticated role-based coordination. Since February 2026 it has shipped v1.0 through v1.2.1, moved to the gastownhall org, spawned the Wasteland federation and Gas City framework, and gained a Kilo-hosted cloud version — but it remains expert-oriented and chaotic by design.
Recommended for: Expert developers (Stage 7-8) who want to explore the frontier of multi-agent orchestration and are comfortable with instability; teams wanting the same model without tmux can try Gas Town by Kilo.
Not recommended for: Anyone seeking production stability, enterprise features, or a gentle learning curve.
Outlook: Gastown has outlasted the "abandonment" skepticism — the Kilo partnership and steady v1.x releases give it commercial backing and reduced bus factor. Its concepts (specialized roles, merge queues, federated agent networks) are already influencing commercial tools.
Research by Ry Walker Research • methodology
Sources
- [1] Welcome to Gas Town - Steve Yegge
- [2] Gastown GitHub Repository
- [3] Gas Town Releases - GitHub
- [4] Gas Town by Kilo is Here, With Wasteland Built In - Kilo Blog
- [5] Gas Town Comes to the Cloud - The New Stack
- [6] Welcome to Gas City - Steve Yegge
- [7] Beads GitHub Repository
- [8] MAKER Benchmark Paper
- [9] Gas Town discussion - Hacker News
- [10] Revenge of the Junior Developer - Sourcegraph