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, 22:15 UTC
docs(orchestration-v2): task_cancel describes queued-only tasks and when it rejects (#34517)
Julius Marminge committed
Nov 11, 2026 at 13:22 UTC
fdcf27211e5d8d42568b92a55024e7111b6620fe
1 file changed
+12
-7
docs/orchestration-v2/orchestrator-mcp-server.md
+12
-7
@@ -328,13 +328,18 @@ the published task result.
328
### `task_cancel`
329
330
Stops every task the child delegated, then the child thread with the internal
331
-`thread.stop` command, and disposes automatic parent delivery. Like a user Stop,
332
-`thread.stop` interrupts the running turn, holds queued turns, and ends pull request
333
-watches. A nonterminal task with no interruptible run is rejected unless its finished
334
-turn still waits on background work or delegated tasks. Once a cancelled task's turn ends,
335
-a completed result settles as `interrupted` and a failed one stays `failed`. A terminal task
336
-returns its existing status, and its child thread still stops, including later
337
-runs and watch wakes. Published task results remain available. It accepts an
331
+`thread.stop` command, cancels the task's own queued turn, and disposes automatic
332
+parent delivery. Like a user Stop, `thread.stop` interrupts the running turn, holds
333
+queued turns, and ends pull request watches. The task's own queued turn is cancelled
334
+even if Stop already held it, so a task that is only queued can be cancelled; other
335
+queued turns in the child stay held for Resume. A nonterminal task is rejected when
336
+it has no interruptible run, no queued turn of its own, and its finished turn no
337
+longer waits on background work or delegated tasks. Once a cancelled task's turn
338
+ends, a completed result settles as `interrupted` and a failed one stays `failed`. A
339
+terminal task returns its existing status, and its child thread still stops,
340
+including later runs and watch wakes. In both cases, a follow-up that lost its child
341
+run but still shows as running on the parent is cancelled there and reported as
342
+`cancelled`. Published task results remain available. It accepts an
343
optional cancellation reason.
344
345
### `create_threads`