Skip to content

Commit c754d31

Browse files
docs(server): align child followup guidance
1 parent a3cfc0c commit c754d31

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

‎docs/orchestration-v2/orchestrator-mcp-server.md‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -244,13 +244,12 @@ omits it for a provider that offers all of them. When the target lists
244244
`runtimeModes`, an explicit `runtimeMode` outside that list is refused, and an
245245
inherited mode steps down to the broadest mode the target offers.
246246

247-
Each delegated review round uses a new `delegate_task` call with the original brief,
247+
Each independent delegated review round uses a new `delegate_task` call with the original brief,
248248
prior findings, responses, and unresolved objections. Track each round by its own `taskId` and use
249249
a distinct `clientRequestId` per round, stable across retries of that round.
250-
`childThreadId` is backing storage, not a target for another review round through
251-
`t3_thread_send`. Ordinary thread messaging remains available for user-requested
252-
conversations; it does not reopen a completed task. There is no task-level follow-up
253-
API for preserving the same reviewer session.
250+
For a follow-up that needs the same child's conversation, use `t3_thread_send` on
251+
its `childThreadId`. After the original task completes, its published result stays
252+
unchanged and later turns are tracked as separate tasks.
254253

255254
Delegation requires an active parent run owned by the MCP credential's
256255
provider session. The request becomes the V2 command

0 commit comments

Comments
 (0)