CodeHerderSearch⌘KRequest access →

CodeHerder vs Gas City / Gasworks

Steve Yegge's programmable agent platform. A durable, Git-backed work tracker plus TOML formulas that become multi-stage agent workflows.

2 November 2026
Last checked
20
Capabilities scored, side by side

Verified against the vendor's own published materials.

What Gas City / Gasworks ships

  • Beads: a Git-backed tracker for durable work units that survive a crash
  • Formulas: workflow definitions that run agents in sequence or in parallel
  • A review pass after each run that checks the result against the plan and fills any gaps
  • Beads Team Server, open to design partners only. Gasworks, a managed layer for many operators, is announced and marked coming soon

Where Gas City / Gasworks is strong

  • It is open source and you can host it yourself. It has a working fan-out-and-review pattern
  • It is very programmable. A team that wants to design its own workflow graph from scratch has room to do so

How CodeHerder differs

  • CodeHerder ships as a configured product. Gas City gives you the parts to build your own factory
  • CodeHerder adds cost and budget tracking and a herd of devices across many machines. It also adds a work hierarchy (initiative, epic, story). Gas City does not publish these
Gas City is a kit for your own software factory. CodeHerder is a software factory that is ready to run.

CodeHerder vs Gas City / Gasworks, capability by capability

Every row traces to the same source as the full matrix, where the full legend lives. In short: "not published" means no public evidence was found, not that the feature is absent. Verified as of 2026-11-02.

Capability comparison between CodeHerder and Gas City / Gasworks across 20 capabilities, current as of 2026-11-02.
CapabilityCodeHerderGas City / Gasworks
Concurrent agentsPublishedPublished
Multi-vendor harnessesPublishedPublished
Customer-owned machinesPublishedPublished
Multi-machine routingPublishedPartial [5]
Automatic work assignmentPublishedPublished
Capability-based routingPublishedPartial (configurable)
Atomic claimingPublishedPartial (work queue)
DependenciesPublishedPublished
Custom workflowsPublishedPublished (fully programmable)
Server-enforced gatesPublishedPublished
Agent handoffsPublishedPublished
Persistent shared memoryPublishedPublished (packs/state)
Live terminal / viewPublishedPublished
Human takeover / steerPublishedPublished
Cost per taskPublished (not Cursor sessions)Not published (as of 2026-11-02)
Cost per stage/modelPublishedNot published (as of 2026-11-02)
Hard $ capPublished (checked periodically)Not published (as of 2026-11-02)
SchedulesPublishedPublished
Webhooks / API / CLIPublishedPublished
Self-host full platformPublished (Enterprise)Published (OSS)
  1. Gas City is self-hostable and OSS, which implies multi-machine capability, but no source found describes an explicit cross-machine routing mechanism the way Orchestratia's multi-server dashboard or Warp Oz's fleet model do.

Sources

Verified against Gas City / Gasworks's own site as of 2026-11-02.

  • Gas City's documentation site
  • Gas City's Gasworks page

Try it on one repository for two weeks.

File a task. An agent builds it. A person reads every request. You see the cost of each task.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close