Guides

Orchestrator

For a job too big for one agent. A lead agent reads the code and splits the work into tasks. You check the plan, then up to four workers build it in parallel and the lead reviews the combined result.

The Orchestrator needs a git project: each worker gets its own worktree. Run git init in the folder first if it isn't a repository.

Run the Orchestrator

Choose Orchestrator
In the composer, click + and choose Orchestrator. Describe the whole job and press Enter.
Check the plan
The lead works read-only and proposes up to 12 tasks. Each task lists its agent, model, the files it expects to touch and what it depends on. You can edit any of them.
Set Parallel workers to 1, 2, 3 or 4 (default 2).
Start it
Choose Confirm & start. Nothing runs before you do. Plan again asks the lead for a new plan; Cancel drops it.
Read the result
Workers run their tasks in their own worktrees, respecting the dependencies. Their work is merged file by file, and then the lead reviews the combined change.

Statuses

Planning: the lead is reading the code.
Waiting for you to confirm: the plan is ready to check.
Workers running
Lead is reviewing the result
Done, or Done, with problems when the lead found issues or a task didn't finish.
Couldn't use the proposal: the lead's plan wasn't usable. Choose Plan again.
Interrupted: ThreadGrid quit while it was running.

The Tasks board

For work you'd rather queue than plan up front, choose Add to Tasks in the same menu and write one task per line. Open the board with ⌘T, or Ctrl+T on Windows. With Autopilot on for a project, ThreadGrid works through the board by itself. Each task can be held, released, marked done, run again or sent to another computer.