[Help] OpenClaw Discord bot connected but not receiving messages (intents show “content=limited”)
Hey everyone — I’m trying to get a local OpenClaw Discord bot integration working and I’m stuck at a weird state where everything looks connected, but the bot does not respond to messages.
---
## Environment
- macOS (local CLI install)
- OpenClaw gateway running locally
- Discord bot added to server
- Node/Discord.js-style integration under the hood
---
## Current Status
- Bot shows ONLINE in Discord
- OpenClaw gateway shows:
- Discord: enabled, configured, running, connected
- Guild + channel IDs correctly mapped in config
- JSON config validates successfully (no syntax errors)
---
## Key log issue
intents: content=limited
---
## Discord Developer Portal settings
- Message Content Intent: ENABLED
- Bot permissions:
- Read Messages
- Send Messages
- Read Message History
---
## Behavior
- Bot is online in server
- No errors in gateway logs
- Messages in Discord produce NO response
- u/mentions do nothing
- No message events appear to reach OpenClaw
---
## What I’ve already ruled out
- JSON/config errors
- Missing guild/channel mapping
- Bot offline/token issues
- Permissions issues
- Restart / gateway issues
---
## Suspicion
OpenClaw appears to be running in a restricted Discord intent mode ("content=limited"), meaning it may not actually be receiving MESSAGE_CREATE events even though intents are enabled in Discord.
---
## Question
Has anyone seen this "content=limited" state before in Discord bot integrations?
Is this typically caused by:
- missing gateway intent in code?
- framework limitation (discord.js / wrapper)?
- or Discord token/scope issue?
Everything appears connected but completely silent right now.