Multi-Agent Routing

Overview

OpenClaw supports multi-agent routing — you can route inbound channels, accounts, or peers to isolated agents. Each agent gets its own workspace directory with per-agent sessions, skills, and memory.

Use Cases

• Personal assistant on WhatsApp + work assistant on Slack
• Different personalities for different channels
• Isolated skills and memory per agent
• Separate agents for different users/teams

Configuration

Configure multi-agent routing in openclaw.json:

{
  "agents": {
    "personal": {
      "workspace": "~/.openclaw/agents/personal",
      "channels": ["whatsapp", "telegram"]
    },
    "work": {
      "workspace": "~/.openclaw/agents/work",
      "channels": ["slack", "discord"]
    }
  }
}

Each agent workspace can have its own SOUL.md, AGENTS.md, skills, and memory files.

Per-Agent Skills

Skills follow a precedence order:

Highest priority:
<workspace>/skills/     — Per-agent skills

Shared across agents:
~/.openclaw/skills/      — Managed/local skills

Lowest priority:
bundled skills           — Shipped with OpenClaw

What's Next?