This guide will help you understand the core building blocks that make MeshAgent a powerful platform for building, deploying, and operating AI agents — collaboratively, securely, and at any scale. By the end of this document you will understand how Agents, Tools, and Rooms work together to create seamless AI powered experiences.
MeshAgent enables people, AI agents, and external capabilities (tools) to meet in a secure Room where they can collaborate in real-time, share context, and work together toward common goals.
Agents are backed by an LLM plus a reasoning loop which allows the agent to continue working until a task is complete.
Agents have rules or system prompts which give them insight into their role (e.g. “You are a Document Writer for MeshAgent, an AI startup that provides the missing infrastructure to scale AI Agents”) and are equipped with tools to help them complete their task (e.g. DocumentCreation tool, WebSearch tool, SendEmail tool, etc.).
Alternatively, you can run agents in your agent framework of choice inside of a MeshAgent Room.
Tools are specialized functions that extend what agents can do beyond basic conversation. MeshAgent ships prebuilt, reusable toolkits for common Room interactions (e.g., file and document handling, media generation, dynamic UI interactions) and high-demand tasks (e.g., web search or document-to-Markdown conversion).
MeshAgent toolkits group together related tools and pass the set of tools to the agent for use.
__init__
and execute
function and should return a specific data type (e.g. TextResponse
, JsonResponse
).MeshAgent Rooms provide a shared workspace for agents and participants to collaborate in real time. Each room includes a participant list, presence tracking, and a mechanism for sharing information. Because MeshAgent is designed for seamless integration, rooms are provisioned on demand as participants connect. This eliminates the complexity of syncing rules and allows agents and people to quickly spin up a shared environment to collaborate in.
Temporary by design
A room is provisioned when the first participant joins and deprovisioned when the last participant leaves. It only exists to facilitate communication during the session.
No state persistence
The MeshAgent admin console logs session activity for debugging, such as which agents participated and what questions were asked. However, the state of the room will be discarded at the end of the session, so any data that should persist after the session ends needs to be written to an external storage provider.
Document management
A room can help participants discover, sync, and share documents when they connect to it, but the room only temporarily stores MeshDocuments in memory while they are open. When documents are modified, or a session ends, the changes are written to an external storage provider. By default, MeshAgent Cloud provides a storage folder (named for the room) where documents are kept. For more complex scenarios, you can configure an existing storage solution using a custom provider and save the documents in your own database or storage buckets.
Check out our Getting Started Guide to connect to your first Room and call in your first agent. Or check out the Python Package Overview for more details on how these concepts come together in code.