openclaw - 💡(How to fix) Fix [Bug]:Discord Message Content Intent content=limited despite being enabled — bot can send but not receive guild messages [2 comments, 3 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Environment

OpenClaw version: 2026.5.4 Node.js: v25.8.0 Platform: macOS 26.3.1 (arm64), Mac Mini @openclaw/discord: 2026.5.4 Issue Summary

Bot connects successfully, appears online in Discord, can send messages via webhook, shows typing indicator when mentioned — but never delivers the actual text response back to the guild channel. DMs work perfectly fine.

Steps to reproduce

Enable Message Content Intent in Discord Developer Portal (confirmed toggled ON) Configure Discord channel in OpenClaw with requireMention: false Send a message in the guild channel (with or without @mention) Bot types for several seconds, then stops — no response appears

Expected behavior

Bot processes the message and sends a text response to the guild channel.

Actual behavior

openclaw channels status shows intents: content=limited Raw Discord API confirms: flags: 565248 → GATEWAY_MESSAGE_CONTENT_LIMITED (524288) is set, GATEWAY_MESSAGE_CONTENT (262144) is NOT set Bot receives zero MESSAGE_CREATE events in guild channels (verified via logs) DMs work — bot receives and responds correctly via DM A serenity (Rust) bot using the same token with GatewayIntents::MESSAGE_CONTENT works correctly on the same server Toggling the intent OFF → save → ON → save does not resolve it Bot re-invited with new OAuth URL after enabling intent Bot has blue checkmark (verified) in Discord Developer Portal

OpenClaw version

2026.5.4

Operating system

Mac mini

Install method

No response

Model

minimax 2.7

Provider / routing chain

openclaw minimax discord

Additional provider/model setup details

Bot is verified, under 100 servers A separate Rust serenity bot with identical token receives guild messages normally Webhook delivery works (cron outputs deliver correctly) This appears to be identical to issue #55594 — OpenClaw may not be correctly requesting the MESSAGE_CONTENT intent bitmask from Discord even when the intent is enabled in the portal

Logs, screenshots, and evidence

[default] Discord Message Content Intent is limited; bots under 100 servers can use it without verification.
discord channels resolved: 1479511210503442442/1479511212273172685 (guild:ProductionX; channel:captain)
discord client initialized as 1501020674804682914; awaiting gateway readiness

Impact and severity

Discord guild channels are completely unusable for bot communication. Workaround is DMs only.

Additional information

No response