High🔗 Connectivity

Discord Bot Joins Server But Reads No Messages — Missing Intents

By Jason GuoPublished July 25, 2026Updated September 5, 2026

// Your OpenClaw Discord bot shows online, responds to slash commands you registered months ago, but completely ignores normal channel messages and DMs. This is the classic Privileged Gateway Intent gap: Discord hides message body content from bots unless Message Content Intent is enabled in the Developer Portal. Some setups also need Server Members Intent for name resolution or role-based routing. The bot is connected — Discord just never delivers the events OpenClaw needs. This unofficial guide covers enabling intents, generating a fresh OAuth invite with bot + applications.commands scopes, updating openclaw.json channel config, and restarting the gateway so message handlers actually fire.

diagnose.sh

🔍 Is This Your Issue?

?Bot shows online in Discord but ignores plain text messages

?Slash commands may work while normal chat does not

?Gateway logs show connection OK but no message handlers firing

?You never enabled Message Content Intent in Discord Developer Portal

?Bot was invited before intents were enabled — same invite reused

portal_intents.md

✅ Fix 1 — Enable Privileged Gateway Intents in Portal

Portal toggles — Message Content is the usual fix

# Browser: discord.com/developers/applications
# 1. Select your bot application
# 2. Bot → Privileged Gateway Intents
# 3. Enable:
#    ☑ MESSAGE CONTENT INTENT (required)
#    ☑ SERVER MEMBERS INTENT (if using roles/names)
# 4. Save Changes

Token lives in OpenClaw config, not in the portal screenshot

# Optional: note your Application ID (Client ID)
# Bot tab → Token → Reset Token only if compromised
# Do NOT share token; set in ~/.openclaw/.env:
# DISCORD_BOT_TOKEN=your_token_here

invite_url.txt

✅ Fix 2 — Regenerate Bot Invite With Correct Scopes

Fresh invite after intent changes

# Generate invite URL (replace CLIENT_ID)
https://discord.com/api/oauth2/authorize?client_id=CLIENT_ID&permissions=2147875840&scope=bot%20applications.commands

# permissions include Send Messages, Read History, etc.
# scope must include bot AND applications.commands

Use URL Generator if you prefer clicking checkboxes

# Re-add bot to server OR kick and re-invite
# OAuth2 → URL Generator in portal is equivalent
# Required scopes: bot, applications.commands
# Bot permissions: Read Messages, Send Messages,
#   Read Message History, Embed Links, Attach Files

openclaw.json

✅ Fix 3 — Update Config & Restart Gateway

Allowlist guild/channel IDs — empty config ignores messages

// ~/.openclaw/openclaw.json — discord channel
{
  "channels": {
    "discord": {
      "enabled": true,
      "tokenEnv": "DISCORD_BOT_TOKEN",
      "guilds": {
        "YOUR_GUILD_ID": {
          "channels": ["YOUR_CHANNEL_ID"]
        }
      }
    }
  }
}

Restart required after portal + config changes

openclaw doctor
openclaw gateway restart

# Send test message in allowed channel
# Watch logs:
openclaw logs --follow | grep -i discord

💡 Pro Tip: Re-invite After Intent Changes

Toggling intents in the portal does not retroactively fix an old guild authorization. Kick the bot or use a fresh invite URL with the same client ID, then verify MESSAGE_CREATE events appear in gateway debug logs before testing agent replies.

🛡️ Prevention Checklist

• Enable Message Content Intent before first production invite — document the portal URL in your runbook
• Store the bot token only in ~/.openclaw/.env or openclaw.json — rotate if pasted into Discord support tickets
• Use separate Discord applications for dev vs prod bots so intent experiments do not break live servers
• After portal changes, always restart gateway and watch logs for GatewayIntentBits warnings
• For 100+ server bots, verify Discord verified-bot requirements for privileged intents

← Node Version Too Old Plugin ContextEngine Crash →

❓ FAQ

Q1. Which intents does OpenClaw Discord need?

At minimum: Guilds, Guild Messages, Message Content (privileged), and Direct Messages. Message Content is the one most people miss — without it, MESSAGE_CREATE events arrive with empty content fields. Server Members Intent helps if your config maps Discord roles to agent permissions or mentions users by display name. Presence Intent is rarely required unless you build presence-aware automations. Check OpenClaw docs for your version's default intent set in the Discord channel adapter.

Q2. The bot reads messages in my test server but not another — why?

Intents are global per application, but channel allowlists in openclaw.json may restrict which guild IDs or channel IDs OpenClaw processes. A missing guild id in channels.discord.guilds means ignore. Also verify the bot role has Read Message History and View Channels in that server's channel overrides. @everyone deny rules silently block bots even when intents are correct.

Q3. Do slash commands work without Message Content Intent?

Yes. Slash commands use interaction events, not message content. Many users think the bot is 'working' because /ping responds while free-text chat is ignored. That pattern almost always means Message Content Intent is off. Enable it, restart gateway, send a plain text hello — not a slash command — to confirm.

Q4. Discord asked me to verify the bot for Message Content — what now?

Discord requires identity verification for bots in 100+ servers using Message Content Intent. Sub-100-server homelab bots usually enable the toggle immediately without review. If you hit the verification wall, either complete Discord's developer verification flow or use slash-only / thread-based triggers until approved. Community Mac Mini setups typically stay under the threshold.

Q5. Where do I put the Discord bot token in OpenClaw?

In ~/.openclaw/openclaw.json under channels.discord.token or via tokenEnv pointing to DISCORD_BOT_TOKEN in ~/.openclaw/.env. Never commit tokens. After token rotation in the portal, update config and restart gateway. Invalid tokens show login failures in logs — different from intent issues where login succeeds but messages are empty.

Q6. How do I confirm intents are working in logs?

Set log_level: debug, restart gateway, send a test message in an allowed channel. Look for MESSAGE_CREATE or discord:message handlers with non-empty content. Warnings like 'Received message with empty content' or intent bitmask errors point back to the portal toggles. Official project: github.com/openclaw/openclaw.