Multi-Agent Systems › Real-World Frameworks

The concepts in this chapter are not just theoretical. Several open-source and commercial frameworks implement them in practical, production-ready ways. Understanding how these frameworks map coordination patterns to code helps bridge the gap between the conceptual discussion above and actual system implementation.

AutoGen (Microsoft Research, 2023) is one of the most widely adopted frameworks for LLM-based multi-agent systems. It provides a ConversableAgent abstraction where agents exchange natural language messages in a chat-like interface, with the framework handling message routing, conversation history, and code execution. AutoGen's GroupChat class implements a peer-to-peer topology where multiple agents take turns contributing to a shared conversation, with a configurable speaker selection strategy that determines which agent responds next. The framework's design philosophy emphasizes flexibility: the same code can run with any LLM backend, and agents can be configured to use human input at specified checkpoints, making it suitable for human-in-the-loop workflows.

LangGraph (LangChain, 2024) takes a different approach, representing multi-agent workflows as explicit state machines where nodes are agents and edges define allowed transitions. This graph-based representation makes the flow of control visible and auditable: you can inspect the graph to understand exactly which agents can execute after which other agents, and the state schema defines precisely what information is available to each agent at each node. LangGraph's explicit state model makes it easier to reason about system behavior and to add persistence (checkpointing the graph state so the system can resume after failures).

CrewAI focuses on hierarchical orchestration with role-based agent definitions. A Crew consists of Agents with defined roles and goals plus backstories, coordinated by a Process (sequential or hierarchical). The framework provides a high-level API that abstracts away many of the coordination details covered in this chapter, which makes it fast to prototype but limits the ability to customize low-level coordination behavior. For teams building systems that fit the standard hierarchical pattern, the abstraction level is appropriate; for teams with unusual coordination requirements, lower-level frameworks provide more control.

Swarm (OpenAI, 2024) introduces the concept of handoffs as a first-class primitive: an agent can transfer control to another agent by returning a handoff instruction, at which point the receiving agent continues the conversation with full context from the sender. This is a lightweight peer-to-peer pattern that avoids the complexity of a full message bus, suitable for workflows where the handoff graph is known in advance and relatively simple. The framework is intentionally minimal. This provides just enough structure for basic multi-agent coordination without abstracting away the LLM API calls themselves.

Each framework embodies different tradeoffs. AutoGen optimizes for flexibility and natural language coordination. LangGraph optimizes for explicit control flow and auditability. CrewAI optimizes for ease of use on standard hierarchical tasks. Swarm optimizes for simplicity and direct API access. Choosing among them involves the same tradeoffs as choosing between coordination topologies: what matters most for your specific task structure, your team's ability to debug the system, and your production reliability requirements.

A practical note on framework selection: the rapid pace of development in this space means that framework capabilities change quickly. Any specific feature comparison will be outdated within months. More durable is the evaluation framework: assess how the tool handles dependency management, how it exposes coordination state for debugging, what it does when agents fail, and how cleanly it integrates with your existing infrastructure. These structural properties change more slowly than surface-level API differences.