@devries-cameron20 / t3code Mirror · read-only / commits / 21df2269bd
Fork 0

The best way to control Claude Code, Codex and more from any computer or phone

Mirrored from https://github.com/Camo67/t3code.git

Synced Nov 21, 06:00 UTC

docs(mcp): document thread launch retries (#38842)

Co-authored-by: Julius Marminge <julius0216@outlook.com>

CCJ committed Nov 20, 2026 at 03:20 UTC 21df2269bd30ccb9ece0f2ee70b673d165a01208
1 file changed +7 -2
docs/orchestration-v2/orchestrator-mcp-server.md
+7 -2
@@ -352,8 +352,13 @@ its own under the environment's Scratch project. A new worktree with `startFromO
352 `startFromOrigin: false`. The new thread may not run with broader runtime or
353 interaction modes than the caller. As for `delegate_task`, a runtime mode the
354 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.
362
363 ### `t3_thread_list`
364