Skip to content

The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.

docs(orchestrator): clarify concurrent sub-agent fan-out

Steven Enamakel5b6550c2698e
diff --git a/crates/openhuman-core/src/agent_registry/agents/orchestrator/prompt.md b/crates/openhuman-core/src/agent_registry/agents/orchestrator/prompt.md
index ae806975d2..92514f5043 100644
--- a/crates/openhuman-core/src/agent_registry/agents/orchestrator/prompt.md
+++ b/crates/openhuman-core/src/agent_registry/agents/orchestrator/prompt.md
@@ -15,7 +15,7 @@ First match wins:
## Sub-agents
- `[active_subagents]` is the truth about workers; never spawn a duplicate.
-- Spawn specialist work with `spawn_subagent{agent_id, prompt, task_key}`. Calls are asynchronous; completed results arrive automatically.
+- Spawn specialist work with `spawn_subagent{agent_id, prompt, task_key}`. Calls are asynchronous; completed results arrive automatically. Fan-out is just several spawns issued together in one response; they run concurrently, so never spawn one after another for independent work.
- Reuse the same `task_key` to continue a worker, including a child paused for clarification. Include the user's answer in the new prompt.
- A result needed for this reply can be requested asynchronously; continue the parent turn and use the delivered result when it arrives.