Dispatch, Panel & sub-agents

Three ways to run work in parallel, from the same composer, without leaving the thread.

Dispatch

Send a task to a child thread. The child gets its own worktree branched from the parent, its own provider and access preset, and runs while you keep working. Its card in the parent transcript shows progress, and when it finishes you can open it, read the diff and press Apply to parent to bring the change into the parent's worktree — undoable from the same card.

1. Describe the task and choose Dispatch from the send menu

   Pick the provider and preset for the child. The parent's rules and a Context Pack go with it.

2. Keep working

   The child runs in parallel. Approvals it needs arrive in the same inbox, labeled with the child's name.

3. Review and apply

   Open the child's pane from the card, review its changes, then Apply to parent — or discard.

Panel: the same task, several models

Panel dispatches one prompt to several providers at once, each in its own worktree. Compare the diffs side by side, pick the one you like, apply it, and discard the rest. It is the fastest way to find out which model is actually better at your codebase on this kind of task.

Sub-agents the provider spawns

When a provider's own agent spawns helpers, they appear as sub-agent cards in the transcript. Open a card to drill into that helper's feed. How much you see depends on the provider's protocol:

• Grok streams children live, and you can message a child directly from its pane.
• Claude Code streams child activity live under the parent tool that spawned it.
• Codex and Antigravity show the child's transcript once it is available.
• Cursor and local models report the result when the child finishes.