Gas City Draft

Gas City, Inc. · reviewed 22 November 2026 · its card

Gas City lets one person hand a body of work to a fleet of coding agents and have it broken into tasks, run in parallel, gated on review and tracked to completion: it "runs teams of coding agents (Claude Code, Codex, Gemini, and others) on your repositories", "the open-source platform for building software factories from teams of coding agents" (S2). Gas City, Inc. stewards it, in the gastownhall GitHub organisation (S1, S2). It is "the platform Gas Town's machinery was extracted into": Gas Town's roles are now configuration in a pack, "so the same engine runs Gas Town, Ralph, or whatever you configure" (S4, S6). It runs as the gc CLI on macOS and Linux, installed from Homebrew, with a supervisor that serves a local web dashboard and a REST API (S2, S15, S11). It is MIT open source and free, "the only spend is the model usage of the agents you run"; the maker's commercial Beads Team Server is a separate product (S4, S1). The latest release seen is v1.5.1, of 24 October 2026, beside a rolling edge pre-release from main (S16, S2). It is an agent host for other makers' harnesses and a client onto their sessions.

An instance of
Agent host, Client
Conforms to
Agent Client Protocol (ACP)

How to read a product card.

Capabilities

A product page in four labelled parts: what it is and who makes it; the capabilities table, with columns term, value, detail and sources, and the values yes, partial, no and unknown shown by the matrix's glyphs; the state of play, dated, newest first; and the sources, each with the date it was read.
How to read a product page. Every product has the same parts in the same order.
CapabilityValueDetailSources
Model Yes Whatever harness each agent picks, "Sixteen built-in harnesses, including Claude Code, Codex CLI, Gemini CLI, Cursor Agent, GitHub Copilot, Sourcegraph AMP, OpenCode, Grok, Kimi Code, and Pi"; a per-agent model option and upstreams such as Bedrock, Vertex or an OpenAI-compatible gateway S4 S7 S8
Session Yes wake_mode "resume" (default) reuses "provider session key for conversation continuity"; after a restart the orchestrator "adopts the live sessions it finds and resumes from the store" S12 S4
Subagent Unknown No agent of its own; its workers are sessions in their own right, and the pages read say nothing of the hosted harnesses' own subagents S3 S10
Agent team Yes A coordinating agent, such as the Gas Town pack's mayor, slings work to other agents, and agents "coordinate through two indirect channels: mail (messages) and slung work" S6 S10
Skill Yes Pack- or role-level skill folders, which "Gas City symlinks … into each agent's provider-specific skill sink", .claude/skills/, .agents/skills/, .gemini/skills/, .opencode/skills/; the pages read name neither SKILL.md nor the specification S5
Instruction file Partial No loader of its own: each agent's context starts from its role's prompt template; a provider's instructions_file names "the filename the provider reads for project instructions", AGENTS.md by default S5 S12
Plugin Yes Packs, imported by name and found through a registry, bring "agents, formulas, and orders, along with skills, commands, MCP configuration"; Gas Town's plugins "become orders" S13 S6
MCP Partial The harnesses are the MCP clients; Gas City catalogues packs' MCP configuration, "list-only today (gc mcp list shows what's catalogued; you wire the servers yourself)", though v1.0.0 added "Provider-native MCP projection for Claude, Codex, and Gemini" S5 S18
Execution environment Yes container: the k8s runtime runs "every session in a Kubernetes pod", and exec:<script> is "how sandbox / micro-VM runtime packs plug in"; locally, tmux is none, its commands "a feature, not a sandbox" S7 S14
Client Yes Terminal (gc session attach, peek, logs), a local web dashboard of "agents and their sessions, beads, mail, formula runs", and outside chat or voice front ends over the API; mobile not mentioned S9 S15 S11
Agent host Yes Its core role: it launches other makers' agent CLIs as sessions it can "start, stop, prompt, and observe", over tmux or ACP, and adopts them after a restart S3 S7 S8
Channel Yes External messaging: a client "posts each turn in" and "the agent is notified"; verified webhooks can target a conversation; gc session nudge types text "straight into a running agent" S11 S12 S5
Cross-session messaging Yes Mail, "a bead (type message)" that "waits in an inbox until read", and nudge, "a direct poke into a live session" S5 S10
ACP Yes As client: session = "acp" drives a harness "over the Agent Client Protocol (JSON-RPC over stdio)", where its provider declares supports_acp = true S7 S12
AHP Unknown Not found None
A2A Unknown Not found None
Bot Partial Not named a bot: an always-on named session (mode="always") has "a stable name … across restarts", a mail inbox, and orders that run formulas on "cooldown, cron, condition, event, or manual" triggers; the pages read give an agent no memory of its own beyond the shared beads S9 S5 S3

State of play

How things stand, newest first, as the card records it.

  • Version 1.5.1, the stable release, supersedes 1.5.0 with bug, security and documentation fixes: "text sent to a Claude session can no longer approve its permission prompt", and multi-city deployments sharing a rig store "stop disturbing each other". S16
  • Version 1.5.0: "Beads (bd), not Gas City, now owns the Dolt process of every new city." S17
  • Version 1.4.2, for Beads 1.3.0 compatibility. S18
  • Version 1.0.0, the "First stable release", with provider-native MCP projection for Claude, Codex and Gemini. S18