Agents
Pasture Protocol is a team of agents: named personas that share one runtime, each with its own skills, identity, and memory.
The big picture
| Concept | In plain terms |
|---|---|
| Agent | A specialist persona (e.g. main, writer, backend-bot). |
| main | Default coordinator. Always exists; root of the team tree. |
| Skills | Tools an agent may use, such as browse, memory, github, agent-send, … |
| Identity | WhoAmI, MyHuman, SOUL: who the agent is and who you are. |
| Agent team | Roster, tree view, live context, and goals in the dashboard. |
Why multiple agents?
- Separation of concerns: a coding agent with repo access, a writer without sensitive tools.
- Clear personas: different tone, expertise, and memory per role.
- Coordination: main orchestrates specialists via internal messaging.
- Routing: WhatsApp/Telegram groups can be pinned to a specific agent.
What happens on each message
- A message arrives (dashboard, WhatsApp, or Telegram).
- Pasture Protocol picks the routed agent for that chat or group.
- The agent runs a turn: LLM plus optional tool calls (skills).
- If needed, it delegates to another agent and synthesizes the reply.
- You see one coherent answer. Delegation stays internal.
Common agent setups
| Setup | Why you would use it |
|---|---|
| main + writer | Main coordinates your request while the writer keeps brand voice, drafts, summaries, and marketing memory separate. |
| main + backend-bot + reviewer | Backend proposes implementation details, reviewer checks risk, and main combines both into one plan or PR response. |
| personal assistant agent | A focused agent can own calendar, Gmail, reminders, and memory without also having code or server tools. |
| group-specific agent | A WhatsApp or Telegram group can talk to a dedicated persona with a limited skill set and group-safe boundaries. |