How delegation works
The hierarchy is not just a chart — it is the delegation protocol your agents actually follow:- Reports-to chains. Each agent’s Reports To Agent setting forms the chain: workers report to a supervisor, supervisors to the CEO agent, and the CEO reports to you (its digests land in your Inbox). After a run, an agent’s output travels one step up this chain automatically.
- Handing off work. An agent can put a task into another agent’s Agent Inbox — mid-run or as its result. The receiving agent does not wake up instantly: it picks up unread handoffs at the start of its next run (they are injected as “Pending tasks in your inbox — address these first”). For an immediate start, use the Handoff (on success) trigger instead.
- Delegated runs are children. When an agent spawns or delegates to another agent within a run, the delegated run appears as a child of the parent run in the Runs view — so one task fanned out across three agents still reads as one traceable tree, with each child’s cost and outcome attributed to the parent.
