You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
swarms/docs/protocol/overview.md

15 KiB

Swarms Protocol Overview & Architecture

This document provides a comprehensive overview of the Swarms protocol architecture, illustrating the flow from agent classes to multi-agent structures, and showcasing the main components and folders within the swarms/ package. The Swarms framework is designed for extensibility, modularity, and production-readiness, enabling the orchestration of intelligent agents, tools, memory, and complex multi-agent systems.


Introduction

Swarms is an enterprise-grade, production-ready multi-agent orchestration framework. It enables developers and organizations to build, deploy, and manage intelligent agents that can reason, collaborate, and solve complex tasks autonomously or in groups. The architecture is inspired by the principles of modularity, composability, and scalability, ensuring that each component can be extended or replaced as needed.

The protocol is structured to support a wide range of use cases, from simple single-agent automations to sophisticated multi-agent workflows involving memory, tool use, and advanced reasoning.

For a high-level introduction and installation instructions, see the Swarms Docs Home.


High-Level Architecture Flow

The Swarms protocol is organized into several key layers, each responsible for a specific aspect of the system. The typical flow is as follows:

  1. Agent Class (swarms/agents)

    • The core building block of the framework. Agents encapsulate logic, state, and behavior. They can be simple (stateless) or complex (stateful, with memory and reasoning capabilities).

    • Agents can be specialized for different tasks (e.g., reasoning agents, tool agents, judge agents, etc.).

    • Example: A ReasoningAgent that can analyze data and make decisions, or a ToolAgent that wraps external APIs.

    • Quickstart for Agents

    • Agent API Reference

  2. Tools with Memory (swarms/tools, swarms/utils)

    • Tools are modular components that agents use to interact with the outside world, perform computations, or access resources (APIs, databases, files, etc.).

    • Memory modules and utility functions allow agents to retain context, cache results, and manage state across interactions.

    • Example: A tool for calling an LLM API, a memory cache for conversation history, or a utility for parsing and formatting data.

    • Tools Overview

    • BaseTool Reference

  3. Reasoning & Specialized Agents (swarms/agents)

    • These agents build on the base agent class, adding advanced reasoning, self-consistency, and specialized logic for tasks like planning, evaluation, or multi-step workflows.

    • Includes agents for self-reflection, iterative improvement, and domain-specific expertise.

    • Example: A SelfConsistencyAgent that aggregates multiple reasoning paths, or a JudgeAgent that evaluates outputs from other agents.

    • Reasoning Agents Overview

    • Self Consistency Agent

    • Agent Judge

  4. Multi-Agent Structures (swarms/structs)

  5. Supporting Components

    • Communication (swarms/communication): Provides wrappers for inter-agent communication, database access, message passing, and integration with external systems (e.g., Redis, DuckDB, Pulsar). See Communication Structure

    • Artifacts (swarms/artifacts): Manages the creation, storage, and retrieval of artifacts (outputs, files, logs) generated by agents and swarms.

    • Prompts (swarms/prompts): Houses prompt templates, system prompts, and agent-specific prompts for LLM-based agents. See Prompts Management

    • Telemetry (swarms/telemetry): Handles logging, monitoring, and bootup routines for observability and debugging.

    • Schemas (swarms/schemas): Defines data schemas for agents, tools, completions, and communication protocols, ensuring type safety and consistency.

    • CLI (swarms/cli): Provides command-line utilities for agent creation, management, and orchestration. See [CLI Documentation] (https://docs.swarms.world/en/latest/swarms/cli/main/)


Detailed Architecture Diagram

The following Mermaid diagram visualizes the protocol flow and the relationship between the main folders in the swarms/ package:

flowchart TD
    A["Agent Class<br/>(swarms/agents)"] --> B["Tools with Memory<br/>(swarms/tools, swarms/utils)"]
    B --> C["Reasoning & Specialized Agents<br/>(swarms/agents)"]
    C --> D["Multi-Agent Structures<br/>(swarms/structs)"]
    D --> E["Communication, Artifacts, Prompts, Telemetry, Schemas, CLI"]
    
    subgraph Folders
        A1["agents"]
        A2["tools"]
        A3["structs"]
        A4["utils"]
        A5["telemetry"]
        A6["schemas"]
        A7["prompts"]
        A8["artifacts"]
        A9["communication"]
        A10["cli"]
    end
    
    %% Folder showcase
    subgraph "swarms/"
        A1
        A2
        A3
        A4
        A5
        A6
        A7
        A8
        A9
        A10
    end
    
    %% Connect folder showcase to main flow
    A1 -.-> A
    A2 -.-> B
    A3 -.-> D
    A4 -.-> B
    A5 -.-> E
    A6 -.-> E
    A7 -.-> E
    A8 -.-> E
    A9 -.-> E
    A10 -.-> E

Folder-by-Folder Breakdown

agents/

Purpose: Defines all agent classes, including base agents, reasoning agents, tool agents, judge agents, and more.

Highlights:

  • Modular agent design for extensibility.

  • Support for YAML-based agent creation and configuration. See [YAML Agent Creation](https://docs.swarms.world/en/latest/swarms/ agents/create_agents_yaml/)

  • Specialized agents for self-consistency, evaluation, and domain-specific tasks.

  • Example:

  • ReasoningAgent, ToolAgent, JudgeAgent, ConsistencyAgent, OpenAIAssistant, etc.

  • Agents Overview

tools/

Purpose: Houses all tool-related logic, including tool registry, function calling, tool schemas, and integration with external APIs.

Highlights:

  • Tools can be dynamically registered and called by agents.

  • Support for OpenAI function calling, Cohere, and custom tool schemas.

  • Utilities for parsing, formatting, and executing tool calls.

  • Example:

  • base_tool.py, tool_registry.py, mcp_client_call.py, func_calling_utils.py, etc.

  • Tools Reference

  • What are tools?

structs/

Purpose: Implements multi-agent structures, workflows, routers, registries, and orchestration logic.

Highlights:

  • Swarms for majority voting, round-robin, hierarchical delegation, spreadsheet processing, and more.

  • Workflow orchestration (sequential, concurrent, graph-based).

  • Utilities for agent matching, rearrangement, and evaluation.

  • Example:

  • MajorityVotingSwarm, HierarchicalSwarm, SwarmRouter, SequentialWorkflow, ConcurrentWorkflow, etc.

  • Custom Multi Agent Architectures

  • SwarmRouter

  • AgentRearrange

utils/

Purpose: Provides utility functions, memory management, caching, wrappers, and helpers used throughout the framework.

Highlights:

  • Memory and caching for agents and tools. See [Integrating RAG with Agents](https://docs.swarms.world/en/latest/swarms/memory/ diy_memory/)

  • Wrappers for concurrency, logging, and data processing.

  • General-purpose utilities for string, file, and data manipulation.

Example:

  • agent_cache.py, concurrent_wrapper.py, file_processing.py, formatter.py, etc.

telemetry/

Purpose: Handles telemetry, logging, monitoring, and bootup routines for the framework.

Highlights:

  • Centralized logging and execution tracking.

  • Bootup routines for initializing the framework.

  • Utilities for monitoring agent and swarm performance.

  • Example:

  • bootup.py, log_executions.py, main.py.

schemas/

Purpose: Defines data schemas for agents, tools, completions, and communication protocols.

Highlights:

  • Ensures type safety and consistency across the framework.

  • Pydantic-based schemas for validation and serialization.

  • Schemas for agent classes, tool calls, completions, and more.

Example:

  • agent_class_schema.py, tool_schema_base_model.py, agent_completion_response.py, etc.

prompts/

Purpose: Contains prompt templates, system prompts, and agent-specific prompts for LLM-based agents.

Highlights:

  • Modular prompt design for easy customization.

  • Support for multi-modal, collaborative, and domain-specific prompts.

  • Templates for system, task, and conversational prompts.

Example:

artifacts/

Purpose: Manages the creation, storage, and retrieval of artifacts (outputs, files, logs) generated by agents and swarms.

Highlights:

  • Artifact management for reproducibility and traceability.
  • Support for various output types and formats.

Example:

  • main_artifact.py.

communication/

Purpose: Provides wrappers for inter-agent communication, database access, message passing, and integration with external systems.

Highlights:

  • Support for Redis, DuckDB, Pulsar, Supabase, and more.
  • Abstractions for message passing and data exchange between agents.

Example:

cli/

Purpose: Command-line utilities for agent creation, management, and orchestration.

Highlights:

  • Scripts for onboarding, agent creation, and management.

  • CLI entry points for interacting with the framework.

Example:


How the System Works Together

The Swarms protocol is designed for composability. Agents can be created and configured independently, then composed into larger structures (swarms) for collaborative or competitive workflows. Tools and memory modules are injected into agents as needed, enabling them to perform complex tasks and retain context. Multi-agent structures orchestrate the flow of information and decision-making, while supporting components (communication, telemetry, artifacts, etc.) ensure robustness, observability, and extensibility.

For example, a typical workflow might involve:

  • Creating a set of specialized agents (e.g., data analyst, summarizer, judge).

  • Registering tools (e.g., LLM API, database access, web search) and memory modules.

  • Composing agents into a MajorityVotingSwarm for collaborative decision-making.

  • Using communication wrappers to exchange data between agents and external systems.

  • Logging all actions and outputs for traceability and debugging.

For more advanced examples, see the Examples Overview.


Swarms Framework Philosophy

Swarms is built on the following principles:

  • Modularity: Every component (agent, tool, prompt, schema) is a module that can be extended or replaced.

  • Composability: Agents and tools can be composed into larger structures for complex workflows.

  • Observability: Telemetry and artifact management ensure that all actions are traceable and debuggable.

  • Extensibility: New agents, tools, and workflows can be added with minimal friction.

  • Production-Readiness: The framework is designed for reliability, scalability, and real-world deployment.

For more on the philosophy and architecture, see Development Philosophy & Principles and Understanding Swarms Architecture.


Further Reading & References

Conclusion

The Swarms protocol provides a robust foundation for building intelligent, collaborative, and autonomous systems. By organizing the codebase into clear, modular folders and defining a logical flow from agents to multi-agent structures, Swarms enables rapid development and deployment of advanced AI solutions. Whether you are building a simple automation or a complex multi-agent application, the Swarms architecture provides the tools and abstractions you need to succeed.