Agents & Cognition · 06.12
Delegate Teams
How an agent hands a bounded task to a resolved teammate and awaits the result, with budget and attribution threaded through so no spend is anonymous.
A single delegate is a synchronous child session
A delegate yield runs the delegated subtask as a real child session, synchronously, to a terminal result, then injects that result back into the parent's tool response — resolved inline, not fired off and forgotten. Depth guards and grant attenuation apply on every delegation, so a chain of delegations can't silently escalate a teammate's permissions beyond what the original caller actually held.
A team runs every member in parallel and synthesizes
delegate_team is the fan-out version: every named member runs as its own delegate concurrently, all awaited together, and the array of results is handed back to the parent to synthesize into one answer. Each member individually reuses the exact same single-delegate machinery — the same depth guard, the same grant attenuation, the same on-demand specialist creation — so a team of five delegates is genuinely five independently-safe delegations, not a separate, less-guarded fast path.