Discord guild messages not reaching OpenClaw on macOS

[pseudo ether]

DMs work, server mentions fail, phantom default account, intents:content=limited, and intermittent Failed to resolve Discord application id
I’m troubleshooting an OpenClaw Discord setup on macOS and I’m stuck with a very specific failure pattern.

What is happening
The bot works in direct messages
The bot does not respond in Discord server channels
Even when the bot is explicitly @mentioned in a guild channel, nothing happens
This is not a general gateway outage, because OpenClaw itself is up and healthy

Environment
OpenClaw running on macOS

[outer mist]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[solemn helm]

First, what does openclaw --version print?

This smells like two overlapping issues:

• intents:content=limited is not cosmetic. For Discord guild messages, OpenClaw docs treat Message Content Intent as required. After enabling it in the Discord Developer Portal, restart the gateway.
• DMs working but guild mentions doing nothing usually means guild ingress is still blocked by OpenClaw config: groupPolicy="allowlist", missing channels.discord.guilds.<serverId>, channel not allowlisted, or requireMention set in the wrong place.
• The intermittent Failed to resolve Discord application id makes me suspicious of a stale/wrong default Discord account. If you have channels.discord.accounts, make sure channels.discord.defaultAccount points at the real bot account, or add accountId to bindings. Old channel-only bindings keep targeting default.

One sneaky gotcha from the docs: if you only set DISCORD_BOT_TOKEN and never created a channels.discord block, Discord guilds still default to allowlist, so guild messages are ignored until that guild is explicitly allowed.

Please paste these outputs:

openclaw --version
openclaw channels list
openclaw channels status --probe

openclaw channels capabilities --channel discord --target channel:<guild-channel-id>
openclaw channels logs --channel discord --lines 150

And a redacted channels.discord config snippet.

Shortest probable fix path:

1. Enable Message Content Intent, then openclaw gateway restart
2. Ensure the guild is allowed, for example:

{
  channels: {
    discord: {

      groupPolicy: "allowlist",
      guilds: {
        "YOUR_SERVER_ID": { requireMention: true }
      }
    }
  }
}

3. If you use multiple Discord accounts, fix channels.discord.defaultAccount / bindings so guild traffic hits the same account that works in DMs.

Docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/channels/discord
https://docs.openclaw.ai/cli/channels
https://docs.openclaw.ai/gateway/configuration

Paste those outputs and I’ll help narrow it down fast.

[pseudo ether]

Hi, I’m debugging Discord channel delivery in OpenClaw and I’ve narrowed it down pretty far.

What works:

• DMs with the bot work fine
• OpenClaw creates/uses the DM session correctly

What does not work:

• Mentions in a server channel do nothing
• Example test: @Yunnie test-canal-123
• No reply, and no inbound guild/channel event seems to show up in logs for that message

[solemn helm]

If no inbound guild event shows up in logs at all, I would stop looking at sessions/prompts and focus on Discord ingress.

At that point it is usually one of these:

1. Message Content Intent is not actually active

   • If your probe says intents:content=limited, fix that first in the Discord Developer Portal, then restart OpenClaw.

2. The bot can DM, but cannot see that guild channel

   • Check bot invite scopes and channel overrides: View Channel, Read Message History, Send Messages.

3. Wrong Discord account is active for guild traffic

   • This matches your “phantom default account” suspicion.
   • If channels.discord.accounts exists, make sure channels.discord.defaultAccount points at the real bot account.
   • Old bindings without accountId still target default.

4. Guild is not allowlisted in OpenClaw

   • If you only set DISCORD_BOT_TOKEN, Discord guilds still default to groupPolicy="allowlist" until you add channels.discord.guilds.<serverId>.

Can you paste just these 4 things?

openclaw --version
openclaw channels list
openclaw channels status --probe
openclaw channels capabilities --channel discord --target channel:<raw-channel-id>

And, if possible, a redacted channels.discord config block.

What I’m specifically looking for in those outputs:

• intents:content=limited → fix Developer Portal intent + restart
• missing channel perms in capabilities → fix invite/channel overrides
• both default and a named Discord account in channels list → fix defaultAccount
• no guilds.<serverId> allowlist entry → add the guild

Docs:
https://docs.openclaw.ai/channels/discord
https://docs.openclaw.ai/cli/channels
https://docs.openclaw.ai/help/faq

If you paste those, I can usually tell which layer is broken pretty quickly.

[pseudo ether]

Fixed!! Thank you… it was point 4