Repository navigation
docs(mcp): document thread launch retries #38842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -352,8 +352,13 @@ its own under the environment's Scratch project. A new worktree with `startFromO | |
| `startFromOrigin: false`. The new thread may not run with broader runtime or | ||
| interaction modes than the caller. As for `delegate_task`, a runtime mode the | ||
| provider does not offer is refused, and an inherited or default one steps down | ||
| to the broadest mode it offers. Launch has no retry key, so inspect existing threads after a failed or lost response before | ||
| launching again. `create_threads` remains the batch option for a shared checkout. | ||
| to the broadest mode it offers. `create_threads` remains the batch option for a | ||
| shared checkout. | ||
|
|
||
| Set `clientRequestId` on the initial launch to make it retryable. After an error | ||
| or a lost reply, resend the same request with the same key in the same MCP | ||
| session. This reuses any thread already created by that request. If the initial | ||
| request had no key, check for the thread before launching again. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Explain how to identify an unkeyed launch, or stop implying that a retry is safe. The guide tells callers to check for the thread before relaunching. The list result gives no field that identifies the launch. Titles can repeat, and
|
||
|
|
||
| ### `t3_thread_list` | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Qualify the batch option for outside clients.
create_threadsis hidden from outside clients, although they can callt3_thread_launch. An outside client following this guidance cannot use the recommended batch tool. State thatcreate_threadsrequires a thread caller. The supplied tool definitions show this visibility restriction.