Examples / AI
How do you diagram a multi-agent AI system?
Updated
User -> Router Agent -> {Research Agent, Code Agent, Analysis Agent}: one entry point dispatching to three specialists. Each specialist draws as its own box and the dispatch animates, so the architecture reads as routing to specialists rather than one long chained pipeline.
THE TEXT THAT DRAWS IT
User -> Router Agent -> {Research Agent, Code Agent, Analysis Agent}Edit it in the box above and the diagram redraws as you type. Export it as an animated GIF, WebM or WebP, or a still PNG. Every format embeds this text, so the file can be read back into the editor.
WHAT IT SHOWS
A Router Agent reads the request and decides which specialist should handle it. The Research Agent searches, the Code Agent writes and runs code, the Analysis Agent works over data. The user talks to one thing; three exist behind it.
The braces put all three specialists in the same column, which says they are alternatives at the same level of the system rather than stages of a pipeline. That distinction matters when you are arguing about a design: a reader who thinks these are sequential will ask why analysis waits for research, and the diagram answers before the question is asked.
Routing is usually the first thing added to a single-agent system, because a prompt that must handle every kind of request gets worse at all of them. Splitting the work lets each specialist carry its own instructions and its own tools.
The catch is that the router is now the weakest link. It sees every request and it has to be right about all of them.
QUESTIONS
- Should the router broadcast to all agents or pick one?
- Both are real architectures. Braces
{…}animate every specialist receiving work at once; swap them for|…|and the animation picks one per pass, closer to intent-based routing. - How do I show results coming back to the user?
- Add a return line such as
Research Agent -> User. Flows play one after another, so the reply animates after the dispatch.
MORE AI PATTERNS
RAG pipeline diagram
Retrieve first, generate second: the ordering is the whole pattern.
User -> Query Agent -> Vector DB -> LLM -> User
ReAct tool-calling diagram
The model decides whether to answer or to call a tool, then comes back.
User -> Agent -> LLM -> |Tool, Response|
Human-in-the-loop diagram
A guardrail decides what ships and what a person looks at first.
User -> Agent -> LLM -> Guardrail -> |Accepted, Review|
MCP architecture diagram
One protocol between an agent and every tool it was never built for.
Agent -> MCP Client -> MCP Server -> |Knowledge Base, Code Sandbox, Memory|
Also on this site: Serverless REST API diagram, Pub/sub fan-out diagram, Queue worker diagram, Event pipeline diagram and Cloudflare Workers diagram. See all 10 patterns.
Chartado is a text-to-diagram tool: you type lines like A -> B, it draws the architecture and animates the flow.