native-agent-swarms

# Native Agent Swarms Use Codex-native collaboration instead of Claude TeamCreate, TaskCreate, SendMessage, tmux, or shared team-state conventions. Keep orchestration in the parent agent and use specialists as leaf workers. ## Gate delegation Delegate only when the user or applicable project instructions authorize subagents. Delegation never expands the user's requested scope or permission to change external state. Before spawning, confirm: - At least two work streams are genuinely independent. - Each worker has a bounded objective and sufficient starting evidence. - Writable files have exactly one owner. - The expected speed or quality gain exceeds coordination overhead. - Available thread capacity can accommodate the team; prefer 2-3 workers and never exceed the configured limit. Stay sequential when tasks share state, one result determines the next, or workers would edit the same files. ## Compose the team Select the narrowest installed custom agents. Typical choices include `planner`, `architect`, `code-reviewer`, `security-reviewer`, `quality-engineer`, `hypothesis-debugger`, `performance-reviewer`, `database-reviewer`, `accessibility-reviewer`, and language reviewers. Use `team-coordinator` only to advise on decomposition. The parent agent remains responsible for spawning, monitoring, resolving conflicts, and final verification. Keep nesting depth at one unless the user explicitly asks for recursive delegation and the runtime configuration safely allows it. ##...