Title: Agent binding not routing to bound agent — messages stay on agent:main despite valid binding
✅Solved
Labels: bug, routing, multi-agent
When configuring a second Discord bot account with a channel binding to a separate agent, messages in the bound channel are routed to agent:main instead of the bound agent. The bound agent's session is never created.
Sentry workspace contents:
SOUL.md — personality and role definition
IDENTITY.md — name/emoji
AGENTS.md — workspace rules and role description
Binding Config:
"bindings": [
{
"agentId": "sentry",
"match": {
"channel": "discord",
"accountId": "sentry",
"peer": { "kind": "group", "id": "1471776865252278284" }
}
}
]
Discord Account Config (relevant parts):
"accounts": {
"jetson": {
"guilds": { "": { "channels": {
"1471776865252278284": { "allow": false }
}}}
},
"sentry": {
"guilds": { "": { "channels": {
"1471776865252278284": { "allow": true, "requireMention": false }
}}}
}
}
What works:
Sentry Discord bot connects and authenticates
Bot has correct Discord permissions in the target channel (ViewChannel, SendMessages, ReadMessageHistory, etc.)
Channel is allowlisted under sentry account, explicitly denied under jetson account
Config validates with zero issues/warnings
What doesn't work:
Messages create a session keyed agent:main:discord:channel:1471776865252278284 instead of agent:sentry:...
Main agent's SOUL.md/workspace is used, not sentry's
Sentry's session store remains empty (zero sessions ever created)
Response uses the sentry Discord bot token (correct bot replies) but with main agent personality
Troubleshooting performed:
Verified Discord permissions via openclaw channels capabilities — sentry has full access, jetson has Missing Access
Verified config is valid, binding present, no warnings
Manually deleted stale agent:main session for the channel from agents/main/sessions/sessions.json + gateway restart — no effect
Confirmed sentry agent session store is empty (agents/sentry/sessions/sessions.json = [])
When configuring a second Discord bot account with a channel binding to a separate agent, messages in the bound channel are routed to agent:main instead of the bound agent. The bound agent's session is never created.
Sentry workspace contents:
SOUL.md — personality and role definition
IDENTITY.md — name/emoji
AGENTS.md — workspace rules and role description
Binding Config:
"bindings": [
{
"agentId": "sentry",
"match": {
"channel": "discord",
"accountId": "sentry",
"peer": { "kind": "group", "id": "1471776865252278284" }
}
}
]
Discord Account Config (relevant parts):
"accounts": {
"jetson": {
"guilds": { "": { "channels": {
"1471776865252278284": { "allow": false }
}}}
},
"sentry": {
"guilds": { "": { "channels": {
"1471776865252278284": { "allow": true, "requireMention": false }
}}}
}
}
What works:
Sentry Discord bot connects and authenticates
Bot has correct Discord permissions in the target channel (ViewChannel, SendMessages, ReadMessageHistory, etc.)
Channel is allowlisted under sentry account, explicitly denied under jetson account
Config validates with zero issues/warnings
What doesn't work:
Messages create a session keyed agent:main:discord:channel:1471776865252278284 instead of agent:sentry:...
Main agent's SOUL.md/workspace is used, not sentry's
Sentry's session store remains empty (zero sessions ever created)
Response uses the sentry Discord bot token (correct bot replies) but with main agent personality
Troubleshooting performed:
Verified Discord permissions via openclaw channels capabilities — sentry has full access, jetson has Missing Access
Verified config is valid, binding present, no warnings
Manually deleted stale agent:main session for the channel from agents/main/sessions/sessions.json + gateway restart — no effect
Confirmed sentry agent session store is empty (agents/sentry/sessions/sessions.json = [])
Solution
Turn up logging briefly so you can see why it’s dropping:
Then reproduce and watch for lines like:
-
-
-
- “Send Messages in Threads”
- Whether it’s a private thread (bot must be added)
- Whether the bot can “View Channel” on the parent (affects parent/thread resolution)
This would perfectly look like “works sometimes” if you sometimes post in the parent channel and sometimes inside threads.
Then reproduce and watch for lines like:
-
discord: drop guild message (mention required...)-
Blocked discord channel ... not in guild channel allowlist-
discord: drop message ... (empty content)B) Thread-specific permissions / visibility
If you’re testing in a Discord thread (and your thread id differs from the parent channel id), bots can behave differently depending on:- “Send Messages in Threads”
- Whether it’s a private thread (bot must be added)
- Whether the bot can “View Channel” on the parent (affects parent/thread resolution)
This would perfectly look like “works sometimes” if you sometimes post in the parent channel and sometimes inside threads.
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,723Members
Resources
Was this page helpful?
