ai/byre
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

Decide the default limits for just-in-time fan-out

Browse Source
This commit is contained in:
Ian Gulliver
2026-10-15 20:36:10 -07:00
parent 5e0271757f
commit 98a05f9a5f
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TODO.md
+1 -3
View File
@@ -32,9 +32,7 @@
- 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; 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.
- Decide the default limits for just-in-time fan-out
Defaults for maximum depth, concurrent spawned stages and per-task usage budget.
`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.
# M7 — Inbox triage