01 / what yardr does
Everything keeps moving. You only get the questions.
The pipeline is yours to set: which steps it has and who works each, agents, scripts, people, or another yardr. When a step is yours, the issue waits on a siding until you answer.
You write it
An issue in one of your repos, typed in yardr or taken from GitHub or Linear.
An agent builds it
In a copy of the repo of its own, with your own login for claude, codex, grok, kimi, kiro, opencode or pi, and commits.
Another reviews it
A second agent reads the change, and sends it back or passes it on.
A script merges it
The merge queue runs your tests on exactly what merges, then merges it.
Every step is recorded: who did what, when, and the notes they left. An agent's step ends with done, changes, question or failed.
How it works, in full02 / starting a yard
Running on your own machine, with your own logins.
- 01
Check the machine.
yardr doctorsays which tools are missing and where to get them. - 02
Talk to the yardmaster.
yardr chatsets the workspace up with you: repos, steps, who works them. - 03
Or start from a pack. Import a way of working, read every file, change what you like.
$ yardr doctor ✓ git found ✓ herdr found ✓ claude logged in · codex not installed: npm i -g @openai/codex $ yardr pack apply starter --depot acme-web 13 files: pack.yaml, flows/default/*, roles/*, scripts/merge-local $ yardr chat yardmaster This repo has 14 open GitHub issues. Shall I take them into the starter line, with claude building and review going to whoever has room? you yes, but security review on anything in auth/ yardmaster Done. 14 issues in backlog, 2 building.
03 / routing
When one subscription runs out, the work moves to the next.
A group mixes models from different providers, each with your own subscription. yardr reads what each one has left and dispatches the next issue to one with room.
| crew member | quota left |
|---|---|
| claude | 64% |
| codex | 22% |
| grok | 81% |
| codex | 40% |
| assembly |
04 / packs
Ways of working, as folders you can read.
starter
Build, review, security review, decide and merge. A train flow for grouped changes.
yardr pack apply starter --depot <depot>contributors
Triage outside issues and pull requests, review them, merge locally. For maintainers.
yardr pack apply contributors --depot <depot>dir
The same line for a plain folder, no git: a release, an onboarding, a piece of writing.
yardr pack apply dir --depot <depot>Ask for an invite.
Station is in preview, by invite. A mail to yardmaster@yardr.dev asks for yours.
Want help setting it up for your team, or something built for you? Get in touch.
Station
Your own hosted workspace, run for you at my.yardr.dev, with its own agents and repos.
Your own login
Agents run with your own login for claude, codex, grok, kimi, kiro, opencode or pi. Station keeps no AI key of its own.
footplate
The desktop app for macOS and Linux puts the questions waiting for you in one window.
Free on your machines
yardr is free to run on your own machines. Station is paid.