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 City

Gas City's `gc` breaks a job into Beads tasks and runs teams of Claude Code, Codex or Gemini agents on them in parallel.

Reviewed by ReviewRamble editors · Updated

View on GitHub Open source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

3.8/5

Gas City turns Gas Town's agent factory into readable configuration on top of Beads, but out of the box it still runs Claude at maximum effort with no permission prompts.

What is Gas City?

Gas City runs teams of command-line coding agents on your repositories from written-down methods called formulas. The orchestrator decomposes a job into beads, the task records of Beads, fans the ready ones out to as many agents as the work allows, holds each step until its dependencies close, gates steps on review and retries failures, all outside your own terminal session. The default setup ships formulas for building features, fixing issues and reviewing pull requests; build-basic plans, reviews the plan, implements in parallel, reviews the code and opens a PR.

It is the platform Gas Town's machinery was extracted into, and it hardcodes no roles: a mayor, reviewer or planner is an agent defined in TOML with a markdown prompt, bundled into reusable packs, so the same engine can run Gas Town's layout or something else. It has 16 built-in harnesses, among them Claude Code, Codex CLI, Gemini CLI, Cursor Agent and GitHub Copilot, and runs sessions in tmux, as subprocesses, over ACP or on Kubernetes. A local dashboard at 127.0.0.1:8372 shows runs, agents and beads.

Gas City is MIT-licensed Go, stewarded by Gas City, Inc., which also offers a commercial Beads Team Server to design partners. v1.5.1 shipped on 24 October 2026.

Is Gas City worth it?

Gas City is the more disciplined successor to Gas Town: the same factory of coding agents, rebuilt as an engine you configure rather than a cast of hardcoded characters. It has about 1,540 GitHub stars, a fraction of Gas Town's 18,800, but it is where the work happens: at least 100 commits in the past month against Gas Town's 13, and a v1.5.1 release on 24 October.

Beads is the spine. A formula materialises as beads that outlive the file and any session; tasks, inter-agent mail, sessions and convoys are all beads that differ only by type; and a crashed agent's beads stay open for a fresh agent to pick up. Progress is therefore inspectable with ordinary `bd` commands, and Beads' own upgrade and ready-flag traps become Gas City's too: v1.5.1 bundles bd 1.3.2. A file-based store (`GC_BEADS=file`) skips Dolt for light use.

Check the permission defaults before you sling work. The builtin Claude harness defaults to `permission_mode = "unrestricted"`, which launches `--dangerously-skip-permissions`, and `effort = "max"`; the Codex harness defaults to `--dangerously-bypass-approvals-and-sandbox`. Unlike Gas Town, each is a one-line setting per agent (acceptEdits, plan, or Codex's read-only sandbox), though the tutorial warns that a read-only agent cannot finish unattended work. The trust-boundaries page is candid: configured commands are a feature, not a sandbox, imported packs count as trusted code, and bead and PR text count as untrusted data. Shell helpers strip secret-looking environment variables, and the dashboard binds to loopback and turns read-only on any other address unless mutations are allowed. v1.5.1 fixed a bug that let text sent to a Claude session press Enter on a pending permission prompt.

The catch: maximum effort with no prompts is the expensive end of every dial, and Gas City publishes no estimate of what a formula run costs; the FAQ says only that the spend is your agents' model usage. It also needs tmux, Dolt, bd and flock, a new city takes a few minutes to settle while printing alarming status messages, and the tracker holds about 1,063 open issues and 726 open pull requests.

Our take: of the two, Gas City is the one you can reason about, because every role is a file you can read and every unit of work is a bead you can query. Setting effort and permission mode in city.toml belongs before the first run, not after the first bill.

Where it earns its place

  • A four-engineer product team with a backlog of feature tickets

    Turn a written feature request into a reviewed pull request

    Sling the request with the build-basic formula; agents plan, review the plan, implement in parallel, review the code and open a PR for a person to merge. Set `effort` to high and a cheaper model for reviewers in city.toml, since the Claude harness defaults to max.

  • A platform engineer who would rather not run agents on laptops

    Run the agent fleet on a Kubernetes cluster

    Switch the session runtime to Kubernetes per agent or rig, keeping tmux as the fallback the docs require. Secrets reach agents only through explicit config, because Gas City's shell helpers strip inherited secret-like variables.

  • The maintainer of a busy open-source repository

    Review incoming pull requests on a schedule

    An order runs a PR-review formula on a timer or an event, with a reviewer agent in plan mode so it cannot edit files. The trust-boundaries page requires pull_request_target workflows to stay metadata-only, which keeps contributor code from running with your tokens.

Before you commit

Setup
`brew install gascity` installs gc with bd, Dolt, tmux, jq and flock; copy your git identity into Dolt, run `gc init ~/my-city --template gascity --default-provider claude`, `gc rig add` a repository and `gc sling` a task. The README puts this at about five minutes.
Integrations
16 harnesses including Claude Code, Codex CLI, Gemini CLI, Cursor Agent, GitHub Copilot, Sourcegraph AMP, OpenCode, Grok, Kimi Code and Pi; tmux, subprocess, ACP, Kubernetes and herdr runtimes; an HTTP API; optional GitHub gates through gh.
Data and privacy
Code and prompts go to the providers your agents use; work lives in Beads (Dolt) under the city and its rigs. The supervisor serves its API and dashboard on 127.0.0.1:8372 and runs read-only on other addresses unless allow_mutations is set.
Cost at scale
The software is free; spend is model usage billed through your own credentials, multiplied by every parallel step, and the Claude harness starts at maximum effort. Gas City, Inc.'s Beads Team Server for teams has no published price.
Limits
Needs tmux even with other runtimes and Dolt 2.6.0 or newer; new cities take minutes to settle; Claude permission prompts are off by default; about 1,063 open issues.

What’s good

  • Roles, formulas and schedules are plain TOML and markdown
  • Work survives crashes as beads you can inspect with bd
  • 16 harnesses and tmux, subprocess, ACP or Kubernetes runtimes
  • Published trust model; dashboard on loopback and read-only elsewhere

What’s not

  • Claude defaults to bypassed permissions and maximum effort
  • No published cost estimate per formula run
  • Inherits Beads' migration and ready-flag traps
  • About 1,063 open issues and 726 open pull requests

Best for

Teams that want several coding agents to plan, build and review work in parallel and are willing to set permissions and models per agent.

Gas City alternatives

Gas City: common questions

Is Gas City worth it?
Gas City turns Gas Town's agent factory into readable configuration on top of Beads, but out of the box it still runs Claude at maximum effort with no permission prompts. We rate it 3.8 out of 5.
How much does Gas City cost?
Free and open source (MIT). Agents bill to your own Claude, Codex or Gemini logins or API keys. Gas City, Inc. offers a commercial Beads Team Server to design partners; prices not published.
What are the downsides of Gas City?
Claude defaults to bypassed permissions and maximum effort; no published cost estimate per formula run; inherits Beads' migration and ready-flag traps; about 1,063 open issues and 726 open pull requests.
Who is Gas City best for?
Teams that want several coding agents to plan, build and review work in parallel and are willing to set permissions and models per agent.
How much does Gas City cost for a team or in production?
The software is free; spend is model usage billed through your own credentials, multiplied by every parallel step, and the Claude harness starts at maximum effort. Gas City, Inc.'s Beads Team Server for teams has no published price.
Is Gas City safe for company data?
Code and prompts go to the providers your agents use; work lives in Beads (Dolt) under the city and its rigs. The supervisor serves its API and dashboard on 127.0.0.1:8372 and runs read-only on other addresses unless allow_mutations is set.
What are the best Gas City alternatives?
The closest alternatives we have reviewed are Gas Town, Claude Squad, Vibe Kanban and Beads.

Answers checked Nov 16, 2026.