multi-agent-patterns

Multi-agent architectures distribute work across multiple language model instances, each with its own context window. When designed well, this distribution enables capabilities beyond single-agent limits. When designed poorly, it introduces coordination overhead that negates benefits. The critical insight is that sub-agents exist primarily to isolate context, not to anthropomorphize role division.

Multi-agent systems address single-agent context limitations through distribution. Three dominant patterns exist: supervisor/orchestrator for centralized control, peer-to-peer/swarm for flexible handoffs, and hierarchical for layered abstraction. The critical design principle is context isolation—sub-agents exist primarily to partition context rather than to simulate organizational roles.

Effective multi-agent systems require explicit coordination protocols, consensus mechanisms that avoid sycophancy, and careful attention to failure modes including bottlenecks, divergence, and error propagation.

Questa competenza deve essere utilizzata quando l'utente chiede di "progettare un sistema multi-agente", "implementare un modello di supervisore", "creare un'architettura swarm", "coordinare più agenti" o menziona modelli multi-agente, isolamento del contesto, trasferimenti di agenti, sub-agenti o esecuzione di agenti paralleli. Fonte: chakshugautam/games.