Discord inbound not reaching OpenClaw agent (outbound OK)
Discord inbound not reaching OpenClaw agent (outbound OK)
Setup:
OS: Windows 11
OpenClaw: 2026.3.2
Agent: agent:main
Discord bot: @gauselt
Guild: 898186923372318720
general: 898186923372318723
#gruppechat: 1478887524566044792
Status
openclaw status → Discord channel: ON / OK
openclaw channels status --probe → Discord default: … works
Outbound works:
message send --channel discord --target general and #gruppechat succeed (ok: true, correct channelId), messages appear in Discord.
Current config (Discord)
"channels": {
"telegram": {
"enabled": true,
"botToken": "${TELEGRAM_BOT_TOKEN}",
"dmPolicy": "pairing",
"groupPolicy": "open"
},
"discord": {
"enabled": true,
"token": "${DISCORD_BOT_TOKEN}"
}
}
Previously I had a Discord guilds/groupPolicy: "allowlist" block in openclaw.json (with explicit users + channels). That config now only exists in:
openclaw.json.bak.2
agents\main\sessions*.jsonl (old logs)
I’ve searched .openclaw for the IDs:
cd $HOME.openclaw
Get-ChildItem -Recurse | Select-String -Pattern "898186923372318723"
Get-ChildItem -Recurse | Select-String -Pattern "1478887524566044792"
Get-ChildItem -Recurse | Select-String -Pattern "783304577302265906"
No other live config files reference them.
Symptom
When users talk in general or #gruppechat:
openclaw logs --follow shows no discord events at all.
The agent never replies, even on @mentions / “Texo”.
At the same time, Telegram for the same agent works perfectly (DM + groups + heartbeat).
Question
Is there a known issue or stale internal state for Discord routing after removing a guilds/allowlist config?
Is there any other place Discord channel/user allowlists are stored that could still be blocking inbound, even though openclaw.json is now “minimal”?
Happy to provide openclaw status and a short logs --follow snippet while sending test messages if that helps.
Setup:
OS: Windows 11
OpenClaw: 2026.3.2
Agent: agent:main
Discord bot: @gauselt
Guild: 898186923372318720
general: 898186923372318723
#gruppechat: 1478887524566044792
Status
openclaw status → Discord channel: ON / OK
openclaw channels status --probe → Discord default: … works
Outbound works:
message send --channel discord --target general and #gruppechat succeed (ok: true, correct channelId), messages appear in Discord.
Current config (Discord)
"channels": {
"telegram": {
"enabled": true,
"botToken": "${TELEGRAM_BOT_TOKEN}",
"dmPolicy": "pairing",
"groupPolicy": "open"
},
"discord": {
"enabled": true,
"token": "${DISCORD_BOT_TOKEN}"
}
}
Previously I had a Discord guilds/groupPolicy: "allowlist" block in openclaw.json (with explicit users + channels). That config now only exists in:
openclaw.json.bak.2
agents\main\sessions*.jsonl (old logs)
I’ve searched .openclaw for the IDs:
cd $HOME.openclaw
Get-ChildItem -Recurse | Select-String -Pattern "898186923372318723"
Get-ChildItem -Recurse | Select-String -Pattern "1478887524566044792"
Get-ChildItem -Recurse | Select-String -Pattern "783304577302265906"
No other live config files reference them.
Symptom
When users talk in general or #gruppechat:
openclaw logs --follow shows no discord events at all.
The agent never replies, even on @mentions / “Texo”.
At the same time, Telegram for the same agent works perfectly (DM + groups + heartbeat).
Question
Is there a known issue or stale internal state for Discord routing after removing a guilds/allowlist config?
Is there any other place Discord channel/user allowlists are stored that could still be blocking inbound, even though openclaw.json is now “minimal”?
Happy to provide openclaw status and a short logs --follow snippet while sending test messages if that helps.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Was this page helpful?
