Report routing — where a finished session's report goes
How a finished session reports to the session it belongs to instead of the owner inbox: who the reader is, what reaches it, when the owner still gets it, and how to opt a session into a group.
On this page
What it is
When a Claude Code session finishes a turn, its final message normally surfaces in the owner's inbox as a Needs-you row. That is right for a session the owner is running by hand. It is wrong for a worker: the lead that started it should read the result, act on it, and only involve the owner when the answer genuinely needs a person.
Report routing is that rule. A session that belongs to another session — because it is linked under it in a group — hands its finished report to the nearest live session above it. The owner sees nothing until the chain is empty.
Who the reader is
The Group tool owns the hierarchy. A session's reader is the nearest entry above it in its
group chain whose state is not ended:
- a live parent reads it;
- if the parent has finished, the nearest live grandparent reads it, and so on up;
- if every ancestor has ended, the report belongs to the owner, with a one-line note saying the session it reports to has ended.
A session with no group parent at all is untouched: it reports to the Overseer slot or crew lead exactly as before. The two are separate. The link is the switch, so a session only routes once a person (or a tool) has deliberately put it in a group.
A crew member or crew lead with a group parent is read by that parent too, not by its crew lead. Linking one of them moves its finished reports, its questions and its cards up the group chain, exactly like any other session; a crew session with no link keeps its crew road untouched, and a Mission V3 crew keeps it whatever its link.
What reaches the reader
- the child's final message, wrapped in a fenced
agent-reportblock and marked as data the reader must not treat as instructions; - the message is cut at 4,000 characters with a visible elision notice, so one report can never flood a lead's context;
- one line saying no reply is needed unless the reader needs something.
Nothing else app-written rides along.
What routes, and what never does
One list decides this, and it is the routing rule's own set: routes are an ordinary finished turn, a question, a merge conflict, and a routable failure — recovery exhausted, a timed-out wait, or a subagent that never came back. Nothing outside that list routes.
Never routes: a plan approval, a pipeline-complete report, a permission prompt (only a person can click it), a turn the owner opened by typing into that session, and a session that still owes a customer email reply.
One delivery, and the safety nets
- One per turn. The turn-end gate, the self-archive sign-off and the status subscriber share one latch, so a lead is never paid for the same report twice.
- The same final twice goes to the owner. A session that already delivered this exact text does not deliver it again; the repeat surfaces so a loop cannot burn turns.
- Sign-off waits. A self-archiving session with a live reader leaves the board only after its report is accepted. A refused delivery leaves it visible with one line explaining why.
- The park can never strand. A routed session is held out of the owner's inbox for at most 30 minutes per reader, renewed only while the reader is live. A dead reader routes the report up to the owner, never into a void.
- A bypass road still routes. A turn settled by the stall watchdog or a startup resume — roads that skip the turn-end chain — is still parked and adopted by the same delivery.
Turning it on
There is no setting and no separate switch: putting a session under a parent with the Group tool is what turns routing on for it. Remove the session from the group and it reports to the person again exactly as before.