Skip to content

Commit 21df226

Browse files
docs(mcp): document thread launch retries (#38842)
Co-authored-by: Julius Marminge <julius0216@outlook.com>
1 parent d3da5c6 commit 21df226

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

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

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -352,8 +352,13 @@ its own under the environment's Scratch project. A new worktree with `startFromO
352352
`startFromOrigin: false`. The new thread may not run with broader runtime or
353353
interaction modes than the caller. As for `delegate_task`, a runtime mode the
354354
provider does not offer is refused, and an inherited or default one steps down
355-
to the broadest mode it offers. Launch has no retry key, so inspect existing threads after a failed or lost response before
356-
launching again. `create_threads` remains the batch option for a shared checkout.
355+
to the broadest mode it offers. `create_threads` remains the batch option for a
356+
shared checkout.
357+
358+
Set `clientRequestId` on the initial launch to make it retryable. After an error
359+
or a lost reply, resend the same request with the same key from the same
360+
provider session. This reuses any thread already created by that request. If the
361+
initial request had no key, check for the thread before launching again.
357362

358363
### `t3_thread_list`
359364

0 commit comments

Comments
 (0)