Friday
Orchestrator

One job, split up.
Every task, who has it, and where it stands.

Make one agent the lead and it splits the job into tasks for the others. The Tasks tab shows them all, and a task isn’t done until it’s checked.

Claude Code splits checkout-v2 into six tasks and proposes a team, with Start the team
  • You start the teamIn a coding thread the lead’s board is a proposal: Start the team, or let the lead do it alone. Nothing is handed out until you press it.
  • Free agents take tasksEach task names the files it owns and what it waits on. Two tasks that run at once can’t own the same file.
  • Checked before doneFriday runs the task’s check or the project’s typecheck. A failure goes straight back. Then another agent reviews it, unless its own tests passed on a small change.
  1. The Tasks tab

    In progress, Up next and Done, with Hold all and Add task. Add a task for whoever is free or a named agent, then edit, reorder, hold, hand off, send back or drop it.

    Team tasks: Cursor and Kilo working on two, four more up next, each waiting on the one before
  2. Agents that ask each other

    Agents tell, ask and wait for each other, claim files and keep shared notes. Every exchange shows in the thread, the answer under the question.

    Maya asks Codex through Claude Code whether the 3-D Secure path is covered by a test, and the answer comes back

The numbers

  • Up to 12 agentsin one session.
  • Up to 24 taskson one board.
  • 15 minutesA quiet task moves to another agent.
  • Sent back twiceat most, before it comes to you.

Questions

Does each task get its own branch?
In Crew rooms, yes. In an ordinary coding thread, tasks share the agents’ folders; give an agent its own worktree if you want it kept apart.
Where do I see every agent at once?
The Agent Board: one card per agent across all your sessions, with Needs you, Working, In review and Ready.

Free and open source.
On your own computer.