Skip to content

Commit 452eb16

Browse files
zainmitchellclaude
andcommitted
docs(server): describe t3_thread_launch retry keys
The launch section said launch has no retry key, but t3_thread_launch accepts clientRequestId and replays the first accepted launch for the same key within the caller's MCP session. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent ec2eba7 commit 452eb16

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -356,7 +356,9 @@ Pass the task in `message`. Project, model, and modes inherit when omitted;
356356
workspace does not. `scratch: true` launches without a project, in a folder of
357357
its own under the environment's Scratch project. For stacked PRs, use the parent branch as `baseRef` with
358358
`startFromOrigin: false`. The new thread may not run with broader runtime or
359-
interaction modes than the caller. Launch has no retry key, so inspect existing threads after a failed or lost response before
359+
interaction modes than the caller. Reusing a `clientRequestId` within the same
360+
MCP session returns the launch it first accepted instead of launching again.
361+
Without a key, inspect existing threads after a failed or lost response before
360362
launching again. `create_threads` remains the batch option for a shared checkout.
361363

362364
### `t3_thread_list`

0 commit comments

Comments
 (0)