Multi-Agent Setup
SimpleClaw supports multiple agents, each with its own workspace, model configuration, and session store. This lets you create specialized agents for different purposes.Why Use Multiple Agents?
- Specialization - Different agents for coding, writing, research, etc.
- Isolation - Separate workspaces and session histories
- Model Optimization - Use different models for different tasks
- Channel Routing - Route specific channels to specific agents
- Cost Control - Use cheaper models for simple tasks
Creating Your First Agent
Agent Configuration
Via CLI
Via Config File
Add agents to~/.simpleclaw/simpleclaw.json:
Routing Messages to Agents
Channel-Based Routing
Route entire channels to specific agents:Account-Based Routing
Route channel accounts to agents:Peer-Based Routing
Route specific users/groups to agents:Routing Precedence
When a message arrives, SimpleClaw checks routing rules in this order:- Peer binding - Specific user/channel/group
- Parent peer - Thread parent
- Guild + roles - Discord guild with role match
- Guild - Discord guild
- Team - Slack team
- Account - Channel account
- Channel - Messaging platform
- Default - Falls back to
mainagent
Agent Workspace Structure
Each agent has its own workspace:Customizing Agent Behavior
AGENTS.md - Core instructions:Agent Collaboration
Agents can communicate using session tools:sessions_list- Discover other agentssessions_send- Message another agent’s sessionsessions_history- Read another agent’s transcript
Example: Specialized Agent Fleet
Coding Agent
Research Agent
Writing Agent
Per-Agent Skills
Install skills specific to an agent:Agent Status
View all agents:Switching Agents Mid-Conversation
Route a message to a specific agent:Troubleshooting
Agent not found
Agent not found
Verify the agent exists:Check config:
Routing not working
Routing not working
Check routing rules:View debug logs:
Agent using wrong model
Agent using wrong model
Update agent model:Or via config:
Next Steps
Custom Skills
Add specialized tools to agents
Voice Setup
Enable voice interaction with agents
Remote Gateway
Run agents on a remote server
Webhooks
Trigger agent runs from external events