Routing
Pasture Protocol decides which agent handles each conversation: private chats, groups, and dashboard sessions.
Private chats (DMs)
On the dashboard, pick the agent from the chat toolbar. On WhatsApp and Telegram DMs, routing follows your channel configuration and the selected agent for that contact.
Group chats
Each WhatsApp or Telegram group can be assigned to one agent on the Groups page. Every message in that group uses that agent's skills and persona. Optional skill deny lists further restrict what the group agent may do.
Tree vs message permissions
- Solid lines in Team tree view = hierarchy (
mainat root). - Dashed arrows = who may
agent-sendto whom, not the same as chat routing.
Routing examples
| Message source | Routing result |
|---|---|
| Dashboard chat with Backend Bot selected | Backend Bot receives the turn with its own identity, skills, memory, and optional LLM configuration. |
| Telegram DM to the owner | The configured Telegram channel receives the update and sends it to the selected/private-chat agent. |
| WhatsApp group assigned to Writer | Writer handles all group messages, constrained by its enabled skills and any group deny list. |
| main delegates to reviewer | The message is internal agent-send traffic, controlled by allow-list arrows, not chat routing. |
Runtime context
- Sessions bootstrap with agent identity files such as SOUL, WhoAmI, and MyHuman.
- Daily chat logs can be searched when the user explicitly asks about past conversations.
- Each agent can have independent skills and optional model configuration.
- Channel routing and agent delegation are separate systems, even though both choose an agent.