Architecture › Architecture
Architecture
Overview
When you send a message, it travels through four steps, then comes back as a reply. This page explains each step and what’s yours to do at each one.
The flow of a message
| Step | What happens | What you see |
|---|---|---|
| 1. Chat | You type a command or mention an agent in the chat app | The message you just sent |
| 2. Gateway | The gateway receives the message from the chat platform and recognizes the mentioned agent | Nothing — this step runs immediately |
| 3. Bus | The message is placed in a queue for that agent | Nothing, unless the agent is busy — then you may wait |
| 4. Agent | The agent reads the message, works on it, then sends a reply | The agent starts replying or asks a follow-up |
| 5. Reply | The reply travels back through the bus and gateway, to the same chat/thread you sent from | The reply appears in the chat |
What each piece is for you
- Gateway — the chat app you talk through (Telegram, Discord, Slack…), configured on the Integrations page of the web app.
- Bus — the channel that moves messages between people and agents; agents don’t talk to the chat app directly, only through the bus.
- Agent — a named AI worker you start with
/agent up; each agent does one job or role.
Where to go next
- Agent Bus — how to send messages, agent names, scopes
- Agent — starting, stopping, watching an agent
- What is the Gateway? — configuring a chat platform
- Reliability — what happens when an agent runs into trouble