Swarm

From goal to coordinated work

1. Choose Swarm in the session composer and select a preset.
2. Describe the goal and concrete acceptance criteria.
3. Review the initial plan’s tasks, dependencies, and file ownership, then dispatch it. Initial dispatch is manual by default.
4. Follow Mission Control as the orchestrator supervises the team. Answer requests for input and inspect the resulting changes and verification.

Enable Auto dispatch in the Swarm composer if you want the initial plan to start as soon as it validates. Follow-up plans use the continuation flow. The orchestrator coordinates scoped workers and reviewers; server-owned supervision continues while every client is closed.

Follow the run

Mission Control brings together the task roster, current activity, coordination messages, and results. Open a task to inspect its conversation. Watch for requests for input, dependency waits, file leases, failed checks, and recovery attempts.

Good to know · Presence and status are observations, not quality scores. Read the final report and the actual changes before accepting the result.

Keep responsibilities clear

The shared coordination feed lets the team surface progress, questions, review findings, and blockers. Task dependencies sequence related work. Declared write footprints and leases reduce overlapping edits, alongside the file-lock system.

Scope work around concrete files or responsibilities. Give dependent tasks the decisions they need instead of asking every worker to independently redesign the same interface.

Set limits

Use the swarm defaults and preset settings to bound task creation, follow-up work, and review or repair attempts. Koyd uses these limits to keep a run from expanding indefinitely. Provider usage still depends on the models, prompts, and tools selected.

Start with Forge

The built-in Forge preset supplies an orchestrator and three editable agents: Builder, Integrator, and Reviewer. It starts with a small task graph, adds integration when needed, and checks the final deliverable against the original acceptance criteria. Configure Forge in Lab → Swarms and its agents in Lab → Agents.

Good to know · Reviewers are agents with tools, not an independent security sandbox. Model decisions and acceptance criteria still need your judgment. No success-rate claim is implied.

Handle interruptions

Read the task’s error and the coordination feed before retrying. Koyd preserves server-owned queues and recovery information, but an interrupted operation may already have changed a file or an external system. Ambiguous work should be reviewed before being retried.