# What is Agent Swarm?

Also called swarm architecture.

An agent swarm is a multi-agent arrangement in which many peer agents work on a shared goal without a central controller, coordinating through local interaction or a shared medium rather than through a directing supervisor. Global behavior emerges from local decisions, which makes swarms flexible but harder to predict and audit than hierarchical designs.

The term is borrowed from swarm intelligence in biology and robotics, where simple agents following local rules produce useful collective behavior. Applied to language model agents it usually means peers that pass work to one another directly, claim tasks from a common queue, or read and write a shared workspace, instead of receiving assignments from a supervisor above them.

The appeal is robustness and scale. No single coordinator becomes a bottleneck or single point of failure, and adding capacity means adding another peer rather than rewriting a plan. Some frameworks use the word more loosely, applying it to any group of agents that hand control to one another, so the label alone says little about the actual topology.

The costs are real. Without a central plan there is no single place that knows whether the overall goal was met, duplicate work is common, and agents can loop by passing a task back and forth. Termination is genuinely hard, so practical swarms add global limits on total steps, elapsed time, or spend.

Swarms are hardest to debug precisely where they are most useful. Behavior depends on interaction order, so the same inputs can produce different runs. Systems that need auditability usually prefer an explicit supervisor or a fixed workflow, reserving swarm style coordination for exploratory or search heavy problems.

## Key points

- Peer agents coordinate without a central controller
- Behavior emerges from local decisions, not a global plan
- Scales and degrades gracefully, but resists prediction
- Termination and duplicate work are the standard failure modes
- Term is used loosely across frameworks

## In practice

A monitoring setup runs eight peer agents against a shared queue of failing alerts. Each claims an alert, investigates, writes findings to a common store, and may enqueue a follow up alert it discovered. No agent directs the others. A global budget stops the whole group after a fixed number of investigations, which prevents a pair of agents from enqueuing work for each other indefinitely.

## Related terms

- [Multi-Agent System](/en/glossary/multi-agent-system)
- [Agent Orchestration](/en/glossary/agent-orchestration)
- [Supervisor Agent](/en/glossary/supervisor-agent)
- [Blackboard Architecture](/en/glossary/blackboard-architecture)
- [Handoff](/en/glossary/handoff)

[Back to the AI Glossary](/en/glossary)