How to use the coordinator
The coordinator runs a plan that is in motion, so you do not start each agent yourself. You start it once, and it works to the plan’s next milestone — for days, if need be.
In the chain, it comes third: idea → daedalus → metis → coordinator → your agents → you.
How it works
- You start it with the plan’s number.
- It starts the workers. For each agent with a ready step, it asks the plan’s metis which tasks one session takes, and starts that agent as a worker inside its own session — one per agent, up to your Mac’s free slots.
- Each worker opens one pull request, to the plan’s own branch. The coordinator merges it there when the tests passed at the push. A worker’s question goes to metis first, and comes to you in Needs you only if metis cannot answer it.
- At the milestone, it opens one pull request from the plan’s branch to main. That one is yours to merge.
Four things to say
zeus run coordinator P-n
Run it in a terminal, in the repository. P-n is the plan’s number.
start Metis
Say it to its one question, when no metis serves the plan. It starts metis inside its own session.
run two <agent> sessions in parallel
Say it when one agent has more ready work than one worker can take. Your words are what lets that agent have a second worker. Never a third.
zeus work slots --limit <n>
Run it to change how many workers your Mac runs at once. It starts at 3, shared by every repository on the Mac.
What it never does
- It never merges to main.
- It never decides a gate, or answers a question for you.
- It never picks a worker’s tasks in metis’s place.
- It never edits code, and never takes a task itself.
Next: the longer story, One command runs the plan →
The guide: Let the coordinator run the plan →