# Files changed · PR \#23206 · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/pull/23206/diffs)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

[docs\(mcp\): document existing recurring-task tools](https://git.cafe/pingdotgg/t3code/pull/23206.md)

Version: 19

Head commit: 551f891efbb4d5a8ca1ee57560f6b4eac800676d

Base commit: defb7e6e6b87d03259745367214db13060fb322b

Comparison base: defb7e6e6b87d03259745367214db13060fb322b

Showing up to 20 entries from this revision. If the pull request changes, reopen the first page before continuing.

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

Status: modified; +24; −3

```diff
@@ -11,8 +11,9 @@
 - create one or more ordinary top-level T3 threads;
 - list a project's threads and incrementally read any thread;
 - rename threads, regenerate titles, and link or unlink pull requests;
-- send or steer follow-up messages; and
+- send or steer follow-up messages;
+- wait for or interrupt ordinary thread runs; and
+- schedule recurring work that runs without an active turn.
-- wait for or interrupt ordinary thread runs.
 
 These are T3 orchestration operations, not provider-native sub-agent APIs.
 Delegated tasks always create a T3 child thread and run. The child receives
@@ -192,7 +193,12 @@
 
 ## Tool Surface
 
+`OrchestratorToolkit` in
-The server exposes eleven orchestration tools.
+[`toolkits/orchestrator/tools.ts`](../../apps/server/src/mcp/toolkits/orchestrator/tools.ts)
+is the authoritative list of orchestration tools. The sections below cover
+delegation and thread tools. `t3_thread_launch` is documented with them but
+registered by the project toolkit in
+[`toolkits/project/tools.ts`](../../apps/server/src/mcp/toolkits/project/tools.ts).
 
 ### `orchestrator_capabilities`
 
@@ -445,6 +451,21 @@
 returned unchanged, and a thread with no active provider turn returns
 `no_active_run`.
 
+### Scheduled tasks
+
+`schedule_task`, `list_scheduled_tasks`, `update_scheduled_task`, and
+`delete_scheduled_task` manage recurring work in the app scheduler. A schedule
+runs its prompt on an interval, at a fixed time in the server's local time
+zone, or on each qualifying webhook request, even when no turn is active.
+Without a signature, anyone with the webhook URL can trigger a run.
+Signature checks, filters, and dedupe can skip a webhook request.
+`bindToCurrentThread` defaults to `true` only when the caller has a thread in
+the task's project; otherwise it defaults to `false`. Bound runs post into
+that thread; unbound runs each launch a fresh thread in the task's project.
+Explicit `bindToCurrentThread: true` without a caller thread in that project
+is rejected. Pausing uses `update_scheduled_task` with `enabled: false`;
+deletion is permanent.
+
 ## Delegated Task Lifecycle
 
 The MCP server is a command ingress into V2. It does not call provider adapters
```