ia-orchestrating-swarms

# Swarm orchestration ## Primitives For Claude Code teams, see [primitives.md](./references/primitives.md). In Codex, use the active collaboration-tool schemas and [codex-quick-reference.md](./references/codex-quick-reference.md); do not assume Claude's team files or task store exist. --- ## Two Ways to Spawn Agents Resolve the host primitives before dispatching: - **Claude Code:** `Task(...)` for short-lived subagents; `Teammate(...)` plus named `Task(...)` for persistent teams. - **Codex:** `spawn_agent(...)` for short-lived subagents; `send_message(...)`, `followup_task(...)`, and `wait_agent(...)` for coordination. Use persistent teammates only when the active Codex environment exposes that capability. - **Other harnesses:** use their native subagent surface. If none exists, execute the units sequentially in the main thread. The comparison and examples immediately below describe Claude's two dispatch modes. Codex uses `spawn_agent` for both one-shot and follow-up work: ```javascript spawn_agent({ task_name: "find_auth", fork_turns: "all", message: "Find the auth entry points and return paths only." }) ``` Never emit a tool name or argument the active harness does not expose. | Aspect | Task (subagent) | Task + team_name + name (teammate) | |--------|-----------------|-----------------------------------| | Lifespan | Until task complete | Until shutdown requested | | Communication | Return value | Inbox messages | | Task access | None | Shared task list | | Team ...