-
-
Notifications
You must be signed in to change notification settings - Fork 52.6k
Closed
Closed
Copy link
Labels
staleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Environment
- OpenClaw version: 2026.2.9
- OS: macOS (arm64)
- Node: v25.5.0
- Slack mode: Socket Mode
Setup
Two Slack apps (accounts) configured in one OpenClaw instance:
default(primary bot) — handles DMs + multiple channelsdevbot(secondary bot) — bound to one private channel
Config (simplified):
{
channels: {
slack: {
accounts: {
default: { botToken: 'xoxb-...primary', appToken: 'xapp-...primary', ... },
devbot: { botToken: 'xoxb-...secondary', appToken: 'xapp-...secondary', requireMention: false, ... }
}
}
},
bindings: [
{ agentId: 'devbot', match: { channel: 'slack', peer: { kind: 'group', id: 'C0ADQ3A2JUQ' } } }
]
}Expected behavior
Messages in channel C0ADQ3A2JUQ should route to the devbot agent (per binding).
Actual behavior
- Both accounts start successfully (
[default] starting provider,[devbot] starting provider, bothsocket mode connected) - Channel messages in
C0ADQ3A2JUQroute toagent:maininstead ofagent:devbot(confirmed via diagnostic lane logs:lane=session:agent:main:slack:channel:c0adq3a2juq) - DMs to the devbot Slack app DO route to devbot correctly
- Human messages (not just bot messages) also fail to route to devbot in the channel
Additional findings
- Initially tried with
accountId: 'devbot'in the binding — same result - Without
accounts.defaultexplicitly defined (onlyaccounts.devbot), the primary bot fails to start entirely — only devbot starts - After adding both as explicit accounts, both connect but channel routing still goes to main
- No
skiporno-mentionlog entries for devbot — it appears devbot never receives the channel message at all
Steps to reproduce
- Create two Slack apps with Socket Mode enabled
- Configure both as accounts under
channels.slack.accounts - Bind a channel to a non-default agent
- Send a message in that channel
- Observe routing goes to default agent, not bound agent
Workaround attempted
None found yet. The only working setup is single-account with agent binding (but then both agents respond as the same Slack bot identity).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
staleMarked as stale due to inactivityMarked as stale due to inactivity