Multi-agent routing: binding matches accountId but session always created under agent:main
I have two agents (main and cos) with separate Discord bot accounts. Config:
json
"agents": {
"list": [
{ "id": "main", "default": true, "workspace": "~/.openclaw/workspace" },
{ "id": "cos", "workspace": "~/.openclaw/workspace-cos", "agentDir": "~/.openclaw/agents/cos/agent" }
]
},
"bindings": [
{
"agentId": "cos",
"match": { "channel": "discord", "accountId": "cos", "peer": { "kind": "group", "id": "<channel-id>" } }
},
{
"agentId": "main",
"match": { "channel": "discord", "accountId": "default" }
}
],
"channels": {
"discord": {
"accounts": {
"default": { "token": "...", "guilds": { "<guild>": { "channels": { "<general-id>": { "allow": true } } } } },
"cos": { "token": "...", "guilds": { "<guild>": { "channels": { "<cos-channel-id>": { "allow": true } } } } }
}
}
}
openclaw agents list --bindings shows the binding correctly:
- cos: discord accountId=cos peer=group:<channel-id>
- main: discord accountId=default
Problem: When I message in the #chief-of-staff channel (cos bot), the session is created as agent:main:discord:channel:<channel-id> instead of agent:cos:discord:channel:<channel-id>. The origin.accountId is correctly "cos", but the session lands under main's workspace so it loads main's SOUL.md/IDENTITY.md.
I've tried:
1. Adding accountId: "cos" to the binding
2. Deleting the stale session file + sessions.json entry and restarting
(recreates under agent:main)
3. Verified cos has its own agentDir with auth-profiles.json
The cos agent has no sessions.json at all β everything routes to main.
Is this expected behavior? Am I missing a config step? Running OpenClaw v2026.2.24 on macOS.
json
"agents": {
"list": [
{ "id": "main", "default": true, "workspace": "~/.openclaw/workspace" },
{ "id": "cos", "workspace": "~/.openclaw/workspace-cos", "agentDir": "~/.openclaw/agents/cos/agent" }
]
},
"bindings": [
{
"agentId": "cos",
"match": { "channel": "discord", "accountId": "cos", "peer": { "kind": "group", "id": "<channel-id>" } }
},
{
"agentId": "main",
"match": { "channel": "discord", "accountId": "default" }
}
],
"channels": {
"discord": {
"accounts": {
"default": { "token": "...", "guilds": { "<guild>": { "channels": { "<general-id>": { "allow": true } } } } },
"cos": { "token": "...", "guilds": { "<guild>": { "channels": { "<cos-channel-id>": { "allow": true } } } } }
}
}
}
openclaw agents list --bindings shows the binding correctly:
- cos: discord accountId=cos peer=group:<channel-id>
- main: discord accountId=default
Problem: When I message in the #chief-of-staff channel (cos bot), the session is created as agent:main:discord:channel:<channel-id> instead of agent:cos:discord:channel:<channel-id>. The origin.accountId is correctly "cos", but the session lands under main's workspace so it loads main's SOUL.md/IDENTITY.md.
I've tried:
1. Adding accountId: "cos" to the binding
2. Deleting the stale session file + sessions.json entry and restarting
(recreates under agent:main)3. Verified cos has its own agentDir with auth-profiles.json
The cos agent has no sessions.json at all β everything routes to main.
Is this expected behavior? Am I missing a config step? Running OpenClaw v2026.2.24 on macOS.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,426Members
Resources
Similar Threads
Was this page helpful?
