Delegating work

There is no button for this. Delegation is something you ask the agent for, and it uses the Workspace tools the runtime gives it.

Ask for it

Say what should be split off and what should come back:

Before you change anything, have a subagent map every call site of
`resolveTarget` and report the file:line list. Keep writing the plan
while it works.

The parent creates the child, sends it that prompt, and continues its own turn. A receipt lands in the transcript; expand it for the child's name and the prompt it was given.

You can also address a child directly. Open its tab and prompt it like any other session — it is one.

Scope it well

A delegated session starts with no memory of the parent's conversation. Anything it needs has to be in its prompt. That is a feature when the sub-task is self-contained and a problem when it is not.

Good candidates:

• Trace how a subsystem works before deciding how to change it.
• Run a focused review pass over a plan or a diff.
• Try two approaches in parallel, then compare before picking one.
• Split a large task into pieces that do not need to share context.

Skip it when one direct conversation would be simpler. A helper you have to brief twice costs more than it saves.

What a child may do

A delegated session holds a narrower role than an ordinary agent. It cannot create workspaces or other agents, and only its parent can message, open, close, or promote it. It can still message ordinary agents to report back.

That role is checked on every call, not granted once at spawn time — so promoting a session changes what it may do on its next turn, with no restart.