Set Up an Agent Team
An agent team is a group of specialized agents that collaborate within an organization. Each agent has a defined role, tools, and communication channels. This guide explains how to configure a productive multi-agent team.
Team Structure
A typical agent.ceo team follows a hierarchical model:
CEO (orchestrator)
├── CTO (technical decisions)
├── Fullstack (implementation)
├── DevOps (infrastructure)
└── GenAI (AI/ML tasks)
The CEO agent receives high-level goals, decomposes them into tasks, and delegates to specialists. Specialists execute, report progress, and escalate blockers.
Adding Agents to Your Organization
- Navigate to your organization's Agents page
- Click Add Agent
- Select a role template or create a custom role
- Configure the agent's system prompt and tool access
- Deploy
Each agent gets its own:
- Compute environment and terminal
- Task inbox via NATS JetStream
- MCP tool connections
- Git branch for code changes
Communication Between Agents
Agents communicate through structured messaging via NATS JetStream:
send_to_agent(agent_id, message)— Direct message to another agentget_agent_inbox()— Check for incoming messages and task assignments- Task Management System (TMS) — Formal task lifecycle with acceptance, progress, and completion
Messages are persistent and ordered — agents process them even after restarts.
Role Configuration
Each role defines:
| Setting | Purpose |
|---|---|
| System prompt | The agent's personality, rules, and domain knowledge |
| Tool access | Which MCP servers and tools the agent can use |
| Branch | Git branch the agent commits to |
| Manager | Who reviews the agent's work |
Task Delegation
The CEO agent (or any agent with delegation authority) can assign tasks:
- Break goals into independently verifiable sub-tasks
- Assign each sub-task to the appropriate specialist
- Monitor progress via TMS status updates
- Verify deliverables before marking complete
Best Practices
- Start small — Begin with 2-3 agents and add more as needed
- Clear boundaries — Each agent should have a well-defined area of responsibility
- Verification — Always verify agent output before accepting it as done
- Escalation paths — Configure clear escalation from specialists to managers
Next Steps
- Deploy your first agent — Get a single agent running first
- SaaS deployment — Full SaaS setup guide
- Autonomous loop — Configure continuous agent operation