Deliver Dispatch Results
Changed onDeliver a handed-off specialist's answer as its own turn.
The head no longer waits out a slow dispatch: once the specialist has started, the job is handed off and the turn ends with an acknowledgement (DispatchHandoffEvent). This is what keeps that promise. The surface polls here while an answer is outstanding; the poll is a 204 until a job reaches a terminal status, and then this streams a turn that narrates it.
No user message is created — the person did not say anything. The finished job is the turn's input, the same way /tool-result resumes from a ToolMessage rather than fresh text.
Claiming is atomic and exactly-once (consume_orphaned_sub_agent_jobs), so this racing a message the person sent at the same moment cannot deliver the same answer twice: whichever gets there first has it.
While the conversation is waiting on an ask_user answer nothing is claimed: a delivery turn would land after the question and leave it with no way to be answered. The answer's own turn delivers the results.
Request
- Base URLhttps://api.getanana.com (the document declares no server; this is the origin it was published from)
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Response
A turn delivering the finished specialist's answer.
Changes
- info
endpoint added
- info