Check or continue a sub-agent
A delegated child reports back on its own, and you can inspect, continue or stop it at any point.
Results arrive by themselves
Delegation runs in the background by default, and Chetty delivers the result to the conversation that started it when the child finishes. Ask for a blocking run only when you cannot continue without the answer.
Do not repeatedly poll a background child. Polling adds turns without making the work finish sooner.
Read a result
Use DelegateStatus for a child that is still running. DelegateResult reads a completed result, and DelegateRead pages through a long one.
While a child runs, its row in the agents rail shows its elapsed time, its generation speed and its last status note, so you can tell a slow step from a stalled one.
Rest the pointer on the child's name to read its task brief. Move into the card to scroll a long brief, or focus the name with Tab and press Tab again to scroll the card with the arrow keys or PageDown. Escape closes the card. The compact agents list also scrolls, so the Stop controls remain reachable in a short window.
Continue the same child
DelegateContinue resumes the child's own conversation, so it keeps the task and everything it has already found. It does not start a new child, and the continued child keeps its existing access rather than gaining more.
A continuation is checked against your access at that moment. From Plan mode, the follow-up runs read-only and only while the child is idle.
Use a continuation for a correction or a follow-up on the same work. For unrelated work, delegate a fresh task instead. See Keep delegated work within scope for the access a continuation is checked against.
Stop a child
Use DelegateStop on a child you no longer need. In web chat, use Stop sub-agent on its row in the agents rail; in the CLI, click the red ✕ at the end of its row in the Sub-agents list, or press Ctrl+X, then k. A stopped child keeps whatever it already produced in its own conversation.
A stop does not kill a foreground command the child is still waiting on. To stop that too, in the CLI press Ctrl+X, then s, and press it again within the interrupt window to kill the command.
When the queue is full
Every sub-agent slot can be busy. A background child then waits in a queue and shows as queued until a slot frees.
Stopping a queued child removes it from the queue, and it never starts. Other queued children move up as slots free.