in their own terms
What the three are for.
yardr owes its ideas and its vocabulary to Beads, Gas Town and Gas City: the bead is where yardr’s work lives too. What follows says where yardr took those ideas, in plain words, with nothing against any of them.
Gas Town is a workspace manager for many coding agents: a town holding rigs, each rig wrapping a repository, with a Mayor coordinating, polecats doing the work, and hooks keeping state in git. Finished work lands through the Refinery, a per-rig merge queue that runs verification gates and merges with a Bors-style bisecting queue.
Gas City is the open-source platform for building software factories from teams of coding agents. You hand it work; it breaks the work into tasks, runs agents on them in parallel, gates each step on review, and tracks everything in a dashboard. How the work gets done is a formula, and the default setup ships formulas for building features, fixing issues, and reviewing PRs.
Shepherdr is mission control for herdr-core, as a layout for the Herdr app: each space has an Assistant that turns what you write into tasks, every task runs as an ordinary herdr-core agent in its own git worktree, can be reviewed by fresh eyes before it merges, and asks you on a card when it needs a decision.
side by side
The four, side by side.
| aspect | the beads world | yardr |
|---|---|---|
| unit of work | Gas Town bundles beads into convoys; Gas City breaks a job into beads that its formulas fan out; Shepherdr turns what you write to a space into tasks. | An issue in a repository. |
| where it runs | Gas Town manages a town workspace of rigs; Gas City runs a configured city with tmux by default and Kubernetes available; Shepherdr runs inside the Herdr app across several machines. | Your own machine, as one binary. |
| what runs the agents | Gas Town runs its roles in tmux by default; Gas City runs agents in tmux by default, with herdr as an optional backend; Shepherdr runs them as herdr-core agents. | herdr, required: yardr starts every agent through it. |
| whose credentials | Your agent CLIs: Gas City asks for one already logged in, Shepherdr starts each with your own permission settings, and Gas Town runs them as its roles. | Your agents, with your logins. |
| who reviews | Gas City gates each formula step on review; Shepherdr gives each task a fresh-eyes review before it merges; Gas Town’s Refinery runs verification gates on each batch. | A second agent, then you where the decision is yours. |
| what decides a merge | Gas Town merges the batches that pass its verification gates; Gas City’s build formula opens a PR; Shepherdr merges through the task’s pull request on GitHub, asking you first by default. | Your tests, run on exactly the commit that merges. |
| the bead, shared | Gas Town keeps its beads in the bd store, and Gas City does by default with a file store as the option; Shepherdr keeps tasks in its own folders. | Beads served over BDP’s Core reads; yardr claims no conformance. |
| licence | Gas Town and Gas City are MIT. Shepherdr’s README says MIT; its LICENSE-herdr file is Apache-2.0. | Source-available; the terms are in the repository. |
The choice is what you want around the bead. To run many agents in a town you manage, to build a factory from formulas, or to steer tasks from inside the Herdr app — those are Gas Town’s, Gas City’s and Shepherdr’s shapes. To file issues in a repository and get them back as reviewed, tested merges is yardr’s.
sources
Where each fact came from.
the beads world
What Gas Town is and its shape: the workspace manager, the town of rigs with a Mayor and polecats, hooks in git, and convoys of beads.
Its Refinery merge queue with verification gates and the Bors-style bisecting queue, its default tmux roles and configured agent CLIs, and the Beads ledger it keeps.
Its MIT licence.
What Gas City is and its shape: the platform for building software factories, work broken into tasks run in parallel, formulas, and the dashboard.
Its tmux default with herdr as the optional backend, Kubernetes as an available runtime, its already-logged-in agent CLI requirement, the beads store with the file option, and the build formula that opens a PR.
Its MIT licence.
What Shepherdr is and its shape: mission control for herdr-core as a Herdr app layout, spaces with Assistants, tasks as herdr-core agents in worktrees, across several machines from one window.
Its fresh-eyes review, the merge through the task’s pull request asking you first by default, its own folders for tasks, and agents starting with your permission settings.
Its MIT licence.
Its separate LICENSE-herdr file is under Apache-2.0.
yardr
An issue per repository, built by one agent and reviewed by a second, merged after its tests pass.
One binary on macOS and Linux, with your own logins.
Every agent started through herdr, which yardr requires.
The tests run on exactly what merges; nothing is pushed unless YARDR_PUSH names a remote.
Core reads served over BDP, with no conformance claimed.
The source-available terms.