openclaw - 💡(How to fix) Fix Discord: intents.messageContent config key missing — Message Content Intent not requestable [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62040Fetched 2026-04-08 03:09:47
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
RAW_BUFFERClick to expand / collapse

Version: 2026.4.2

The channels.discord.intents config only exposes presence and guildMembers. No messageContent key exists, so the gateway never requests the Message Content privileged intent on connect. Discord returns GATEWAY_MESSAGE_CONTENT_LIMITED (bit 15) but not GATEWAY_MESSAGE_CONTENT (bit 14) even when the portal toggle is enabled.

Expected: Add channels.discord.intents.messageContent: true config key.

extent analysis

TL;DR

Adding the channels.discord.intents.messageContent: true config key may resolve the issue with requesting the Message Content privileged intent.

Guidance

  • Verify that the Discord portal toggle for Message Content is enabled, as this is a prerequisite for the intent to work.
  • Check the Discord documentation to ensure that the messageContent intent is properly configured and enabled for your application.
  • Add the suggested config key channels.discord.intents.messageContent: true to your configuration and test if the gateway returns the expected GATEWAY_MESSAGE_CONTENT (bit 14) response.
  • If the issue persists, review the Discord API and intent configuration to ensure that all requirements are met.

Notes

The solution assumes that the Discord API and intent configuration are correctly set up, and the issue is solely related to the missing messageContent config key.

Recommendation

Apply workaround: Add the channels.discord.intents.messageContent: true config key, as this directly addresses the reported issue with the missing intent configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING