From f84b1788ae08b3c58df54eddcd242a1a161d3a6d Mon Sep 17 00:00:00 2001 From: Ian Gulliver Date: Thu, 15 Oct 2026 20:38:25 -0700 Subject: [PATCH] Drop limit settings from the just-in-time fan-out TODO item --- TODO.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/TODO.md b/TODO.md index e1a2559..e5b4c16 100644 --- a/TODO.md +++ b/TODO.md @@ -31,8 +31,8 @@ Forking a snapshot into a different vendor: the new session starts from a handoff bundle from `export_context` instead of the vendor's native fork, and the UI labels it a handoff, not a true fork. Same-vendor forks from a snapshot exist (see "Forking" in `docs/operations.md`). - Fork-and-compare A fan-out of N forks with different vendors or prompts from one snapshot, followed by a judge stage that produces a comparison with visuals. -- Just-in-time fan-out with limits - `spawn_stages(stages[])` and `collect(stage_ids[])` MCP tools let agents build workflows on the fly, using the same stage definition format. Limits on maximum depth, concurrent spawned stages and per-task usage budget, all configurable and unlimited by default; an optional per-workflow human gate on spawning. Spawned stages show in the task's UI tree marked as just-in-time, and a just-in-time structure can be saved as a reusable workflow. +- Just-in-time fan-out + `spawn_stages(stages[])` and `collect(stage_ids[])` MCP tools let agents build workflows on the fly, using the same stage definition format. An optional per-workflow human gate on spawning. Spawned stages show in the task's UI tree marked as just-in-time, and a just-in-time structure can be saved as a reusable workflow. # M7 — Inbox triage