Capacity first
Before routing, Swarm checks what each machine and agent can safely handle. That prevents overloading one worker while another sits idle.
Memory Hive extension
Hive Swarm routes the work without losing the memory.
Use Swarm when jobs need multiple agents, machines, or capabilities. Memory Hive stays the source of context; Swarm decides who should act.
MissionOne request enters with memory context.
Mac agentFast shell and browser tasks.
Knox agentGPU and heavier creative work.
ReviewerChecks proof before completion.
HiveStores lessons after the run.
Route intentionally
Tasks move to agents with the right capability: browser QA, shell work, creative rendering, review, or deployment.
Write back to memory
Finished work produces proof and reusable lessons that return to Memory Hive instead of disappearing in chat history.
When to use it
Single agent vs swarm execution.
| Single agent | Good for direct edits, small audits, and one-machine tasks. |
|---|---|
| Swarm | Better for parallel QA, multi-machine routing, GPU work, or reviewer loops. |
| Memory Hive | Required foundation for both modes. |