swarming

What problem does it solve?

Swarming ensures multi-agent execution does not stall by continuously tending a coordination runtime, enforcing startup acknowledgments, monitoring worker reports, handling file conflicts, and escalating only when human judgment is required.

Core Features & Use Cases

• Orchestrator-only role: Launches bounded worker subagents, monitors their inbox-driven lifecycle, and never implements beads directly.
• Robust monitoring loop: Poll-act-repeat inbox and topic checks, live bead graph verification, silence ladder reminders, and coordinator handoffs when context is high.
• Coordination primitives: Startup acknowledgments with two-name identity, completion and blocker reports, file reservation coordination, and overseer broadcasts for shared corrections.
• Use Case: Run a coordinated swarm to implement a phase of feature work where multiple workers must reserve files, report completion, and avoid conflicting edits while the orchestrator ensures continuous progress.

Quick Start

Start a coordinated swarm for the current phase by initializing the coordination runtime, spawning bounded workers with the provided worker prompt template, and keep polling inboxes and the bead graph until execution completes.