Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

Gas Town

Steve Yegge's `gt` orchestrator: a Mayor agent files Beads tasks and hands them to a fleet of coding agents in tmux and git worktrees.

Reviewed by ReviewRamble editors · Updated

View on GitHub Open source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

3.3/5

Gas Town shows a Mayor and a crew of agents can work a backlog unattended, but it burns tokens fast, skips every permission prompt and has handed its future to Gas City.

What is Gas Town?

Gas Town runs a fleet of command-line coding agents against one or more git repositories from a single workspace, by default ~/gt. You talk to the Mayor, a Claude Code session that breaks a request into Beads tasks, groups them into convoys and slings each one to a polecat, a worker agent with its own git worktree. A Witness agent per repository watches for stuck workers, a Deacon patrols across projects, and a Refinery merges finished branches through a bisecting merge queue, so workers never push to main themselves. The README pitches it as comfortable at 20 to 30 agents.

It ships presets for Claude Code, Codex, Gemini CLI, GitHub Copilot, Cursor, Kiro, Amp, OpenCode and others, with Claude Code as the default runtime. Work state lives in Beads, a Dolt database and git; `gt up` starts Dolt, a Go daemon and the long-running agents in tmux. Gas Town v1.0.0 shipped on 3 April 2026, the same day as Beads 1.0. It is MIT-licensed Go under the gastownhall organisation, whose maintainers have since extracted its machinery into Gas City, where Gas Town's roles become a configurable pack.

Is Gas Town worth it?

Gas Town is a serious attempt at a factory of coding agents, and an expensive, permissive one: it assumes you will hand a request to an AI coordinator and let a dozen or more agents work it with their safety prompts switched off. The repository has about 18,800 GitHub stars; v1.0.0 arrived on 3 April 2026 and the latest release, v1.2.1, on 6 June.

Read the presets before running `gt up`. In the source, the Claude preset launches `claude --dangerously-skip-permissions`, Codex runs with `--dangerously-bypass-approvals-and-sandbox`, Gemini with `--approval-mode yolo`, Copilot with `--yolo` and Kiro with `--trust-all-tools`. Each polecat can therefore run any command your user account can, in a worktree of your repository, with your git and GitHub credentials. The Docker Compose setup, built on Anthropic's Claude Code sandbox template with a non-root user, is the safer way to try it. The dashboard binds to 127.0.0.1 on a normal install and to 0.0.0.0 inside the container, and the Docker guide says to keep that forwarded port on localhost.

Cost is the other headline. Tim Sehn of DoltHub wrote in January that one hour cost him about $100 in Claude tokens, roughly 10 times a normal Claude Code session, and that Yegge himself warns it burns money. The default cost tier puts Opus on every role, including the patrol agents that only watch the others; the economy and budget tiers move patrols to Sonnet or Haiku, and `scheduler.max_polecats` caps concurrent workers, which are unlimited by default.

The catch: the early reports are rough, and the project's energy has moved. Sehn's first autonomous pull request was merged with integration tests failing, and he closed all four as unusable; Maggie Appleton called it poorly designed. Those were January builds, before 1.0. There has been no release since June, and in our reading of the commit log the 13 commits of the past month are dependency and security fixes, while new orchestration work lands in Gas City. About 394 issues and 131 pull requests are open.

Our take: Gas Town is best read as the working prototype of an idea that now has a better-maintained home. People already running it can carry on, but a team starting today gets the same Beads-backed roles, with permission settings per agent and an active release line, from Gas City.

Where it earns its place

  • A staff engineer on a Claude subscription with a backlog of small, independent bugs

    Clear a batch of fixes overnight without opening each one

    Describe the batch to the Mayor, which files Beads tasks and slings them to polecats; the Refinery merges the branches that pass its verification gates. Set the economy cost tier and `scheduler.max_polecats` first, or rate limits and the bill arrive quickly.

  • A platform team weighing whether to build its own agent orchestration

    See how a coordinator, watchdogs and a merge queue behave in practice

    Run the Docker Compose image against an empty folder, add one throwaway repository as a rig and watch `gt feed --problems` for stalled and zombie agents. Gas City's docs map every Gas Town role to its configuration, so the lessons carry over.

  • A developer who uses both Claude Code and Codex

    Send each task to whichever agent suits it

    `gt sling <bead> <rig> --agent codex` overrides the runtime for one task, and `gt config agent set` adds custom commands such as a lower-effort Codex profile. Each runtime bills to its own account.

Before you commit

Setup
`brew install gastown` installs gt, bd and Dolt on macOS; Linux and Windows use `go install` plus Dolt and tmux. Then `gt install ~/gt --shell --git`, `gt up`, `gt doctor --fix`, `gt rig add` and `gt mayor attach`; Docker Compose is the sandboxed alternative.
Integrations
Agent presets for claude, gemini, codex, kiro, cursor, auggie, amp, opencode, copilot, pi and omp; Beads for work state; OpenTelemetry export; Wasteland federation between towns through DoltHub.
Data and privacy
Code and prompts go to whichever agent providers you configure; state stays in ~/gt, Dolt and git. OpenTelemetry is off unless GT_OTEL_METRICS_URL or GT_OTEL_LOGS_URL is set. Agents run with permission prompts disabled and with your git credentials.
Cost at scale
The software is free; the bill is tokens. The standard tier runs Opus on every role, watchdogs included, and one early user put an hour alongside about 20 agents at roughly $100. Economy and budget tiers and a polecat cap cut that down.
Limits
The full workflow needs tmux, and native Windows is CLI-only; rig names cannot contain hyphens; the last release is v1.2.1 from June 2026; about 394 open issues.

What’s good

  • Coordinator, workers, watchdogs and merge queue already wired together
  • Work state survives crashes in Beads and git worktrees
  • Runs a mixed fleet: Claude Code, Codex, Gemini, Copilot and more
  • Bisecting merge queue keeps workers off main

What’s not

  • Built-in presets switch off every agent's permission prompts
  • Opus on every role by default; about $100 an hour in one early report
  • No release since June 2026; new work goes to Gas City
  • Heavy vocabulary (polecats, convoys, molecules) and tmux required

Best for

Experienced Claude Code users with a large token budget who want to watch a fully autonomous multi-agent workflow and can run it in a container.

Gas Town alternatives

Gas Town: common questions

Is Gas Town worth it?
Gas Town shows a Mayor and a crew of agents can work a backlog unattended, but it burns tokens fast, skips every permission prompt and has handed its future to Gas City. We rate it 3.3 out of 5.
How much does Gas Town cost?
Free and open source (MIT). Every agent bills to your own Claude, Codex, Copilot or other subscription or API key, and a fleet multiplies that bill.
What are the downsides of Gas Town?
Built-in presets switch off every agent's permission prompts; opus on every role by default; about $100 an hour in one early report; no release since June 2026; new work goes to Gas City; heavy vocabulary (polecats, convoys, molecules) and tmux required.
Who is Gas Town best for?
Experienced Claude Code users with a large token budget who want to watch a fully autonomous multi-agent workflow and can run it in a container.
How much does Gas Town cost for a team or in production?
The software is free; the bill is tokens. The standard tier runs Opus on every role, watchdogs included, and one early user put an hour alongside about 20 agents at roughly $100. Economy and budget tiers and a polecat cap cut that down.
Is Gas Town safe for company data?
Code and prompts go to whichever agent providers you configure; state stays in ~/gt, Dolt and git. OpenTelemetry is off unless GT_OTEL_METRICS_URL or GT_OTEL_LOGS_URL is set. Agents run with permission prompts disabled and with your git credentials.
What are the best Gas Town alternatives?
The closest alternatives we have reviewed are Gas City, Claude Squad and Beads.

Answers checked Nov 16, 2026.