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, 23:30 UTC
docs(mcp): t3_thread_update lists only its rename and title actions (#26130)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Julius Marminge committed
Nov 11, 2026 at 11:23 UTC
bc9c84e4f64133a703ec118e0f650b358248c23b
1 file changed
+4
-4
docs/orchestration-v2/orchestrator-mcp-server.md
+4
-4
@@ -427,10 +427,10 @@ runs, background wakes, and delegated completions keep it snoozed.
427
### `t3_thread_update`
428
429
Updates metadata for the calling thread or any other thread in the environment.
430
-The typed actions are `rename`, `regenerate_title`, `link_pull_request`, and
431
-`unlink_pull_request`. A link input supplies the repository, number, and URL;
432
-the server records the target thread's project ID. Branch and workspace changes
433
-are outside this tool.
430
+The typed actions are `rename`, which requires `title`, and `regenerate_title`,
431
+which rejects one. Pull request links go through the separate
432
+`link_pull_request` and `unlink_pull_request` tools. Branch and workspace
433
+changes are outside this tool.
434
435
The result includes the command ID and durable event sequence together with the
436
resultant title, title-regeneration marker, and linked pull request. Reusing a