The best way to control Claude Code, Codex and more from any computer or phone
docs(mcp): document existing recurring-task tools (#23199)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Julius Marminge committed
Nov 2, 2026 at 18:33 UTC
46212dd60e2187ff69694b1fb1025b6acbd885e3
1 file changed
+25
-3
docs/orchestration-v2/orchestrator-mcp-server.md
+25
-3
@@ -11,8 +11,9 @@ agent can use this endpoint to:
11
- create one or more ordinary top-level T3 threads;
12
- list a project's threads and incrementally read any thread;
13
- rename threads, regenerate titles, and link or unlink pull requests;
14
-- send or steer follow-up messages; and
15
-- wait for or interrupt ordinary thread runs.
14
+- send or steer follow-up messages;
15
+- wait for or interrupt ordinary thread runs; and
16
+- schedule recurring work that runs without an active turn.
17
18
These are T3 orchestration operations, not provider-native sub-agent APIs.
19
Delegated tasks always create a T3 child thread and run. The child receives
@@ -196,7 +197,12 @@ provider selection model-visible without allowing a request that cannot run.
197
198
## Tool Surface
199
199
-The server exposes eleven orchestration tools.
200
+`OrchestratorToolkit` in
201
+[`toolkits/orchestrator/tools.ts`](../../apps/server/src/mcp/toolkits/orchestrator/tools.ts)
202
+is the authoritative list of orchestration tools. The sections below cover
203
+delegation and thread tools. `t3_thread_launch` is documented with them but
204
+registered by the project toolkit in
205
+[`toolkits/project/tools.ts`](../../apps/server/src/mcp/toolkits/project/tools.ts).
206
207
### `orchestrator_capabilities`
208
@@ -458,6 +464,22 @@ Without `runId`, it selects the newest interruptible run. A terminal run is
464
returned unchanged, and a thread with no active provider turn returns
465
`no_active_run`.
466
467
+### Scheduled tasks
468
+
469
+`schedule_task`, `list_scheduled_tasks`, and `delete_scheduled_task` manage
470
+recurring work in the app scheduler; `schedule_task` with a `scheduledTaskId`
471
+updates an existing task. A schedule
472
+runs its prompt on an interval, at a fixed time in the server's local time
473
+zone, or on each qualifying webhook request, even when no turn is active.
474
+Without a signature, anyone with the webhook URL can trigger a run.
475
+Signature checks, filters, and dedupe can skip a webhook request.
476
+`bindToCurrentThread` defaults to `true` only when the caller has a thread in
477
+the task's project; otherwise it defaults to `false`. Bound runs post into
478
+that thread; unbound runs each launch a fresh thread in the task's project.
479
+Explicit `bindToCurrentThread: true` without a caller thread in that project
480
+is rejected. Pausing uses `schedule_task` with `scheduledTaskId` and `enabled: false`;
481
+deletion is permanent.
482
+
483
## Delegated Task Lifecycle
484
485
The MCP server is a command ingress into V2. It does not call provider adapters