Fix OpenClaw Discord Bot Not Responding: Silent Bot Diagnosis

Key takeaways

• A bot that's online but silent is a different problem from gateway error 4014. The connection is fine. Something is blocking message processing.
• Check the logs for "drop" lines first. They name the exact reason the bot ignored a message.
• Every Discord server needs its own pairing approval. Approving one guild doesn't cover others.
• Server Members Intent is required for OpenClaw to track server membership. Without it, the bot connects but can't process messages.
• If the bot replies in DMs but not servers, the guild pairing isn't approved or the guild isn't in the allowlist.

Your OpenClaw Discord bot shows up online in the member list. No error on startup, no crash, gateway is running. But when you send a message, nothing comes back. The fix depends on what's blocking replies, and the logs tell you which one it is.

How to diagnose an OpenClaw Discord bot that won't respond

The fastest path to an answer is watching the logs while you send a test message. Most silent bot issues produce a specific log line that identifies the cause directly.

Step 1: Watch logs while messaging

openclaw logs --follow

Send a message in a channel where the bot has access. Look for two things: a line showing the message was received, and any "drop" line explaining why it was ignored.

If the bot received the message, you'll see something like:

Received message from user 123456789 in guild 9876543210987654321

If you see nothing at all when a message is sent, the bot isn't receiving messages. This usually means Server Members Intent is missing or the guild isn't in the allowlist.

Step 2: Look for drop lines

Drop lines appear when the bot receives a message but decides not to process it. They're specific enough to point directly at the fix.

If you see a drop line, you know exactly what to fix. Skip to the relevant section.

Step 3: Check gateway status

openclaw gateway status

If the gateway is running but you see no log activity when messaging, the bot likely isn't receiving messages. Jump to the Server Members Intent section or check gateway error 4014.

Step 4: Check your AI provider

The bot receives the message and logs it, but no reply appears. Look for lines mentioning your AI provider (Anthropic, OpenAI, etc.) with status codes like 401 or 429. A bad API key or exhausted credits stops reply generation. This isn't a Discord problem.

OpenClaw Discord pairing not approved

OpenClaw requires explicit pairing approval before your bot responds in any Discord server. This applies to every guild separately. It's the same pairing system as Telegram, but Discord calls the entity a guild rather than a group.

When the bot joins a server, the logs record a pairing request:

Pairing request from guild 1234567890123456789 (My Discord Server)

The bot won't respond until you approve it. Check what's pending:

openclaw pairing pending

Approve the guild:

openclaw pairing approve discord 1234567890123456789

Use the guild ID from the log line exactly. After approval, the bot responds to messages in that server immediately, no restart needed.

If nothing shows in pending, the bot may need a fresh invite. Kick and re-invite to trigger a new pairing request.

List all currently approved pairings:

openclaw pairing list

This shows which guilds are active. If your server isn't there, it needs approval.

Why your OpenClaw Discord bot needs server members intent

Server Members Intent lets OpenClaw track who's in a server and verify that messages are coming from actual guild members. Without it, the bot connects to Discord but can't reliably process incoming messages.

This is a privileged intent. Discord doesn't enable it by default. You have to turn it on in the developer portal.

When Server Members Intent is missing, the logs show a clean connection, then silence. No 4014 error. That code is specifically about Message Content Intent. Server Members Intent failure is quieter.

What it looks like when the intent is missing and a message is sent:

Discord channel started
Logged in as YourBotName#1234

And then nothing when a message arrives. No received line, no drop line.

Enable Server Members Intent in the Discord developer portal, then restart the gateway:

openclaw gateway restart

The gateway error 4014 guide covers the full portal walkthrough for all three privileged intents, including how to verify they're working after restart.

OpenClaw Discord bot works in DMs but not in servers

If the bot replies to direct messages but stays silent in servers, the guild pairing is the first thing to check. DMs and server messages are separate in OpenClaw's pairing system. Approving a DM doesn't approve any guilds.

Run this:

openclaw pairing list

Look for the server's guild ID. If it's not there, check pending approvals and approve it:

openclaw pairing pending
openclaw pairing approve discord YOUR_GUILD_ID

If the pairing is already approved and the bot still doesn't reply in the server, there are a few other common causes.

Guild not in allowlist. OpenClaw's config has a guilds array. If the array isn't empty and your server's ID isn't in it, the bot ignores that server entirely, even with a valid pairing. The guild allowlist guide covers how to configure this.

requireMention is enabled. By default, the bot only responds when mentioned directly, like @YourBotName or as a reply to its own messages. This behavior is intentional in servers to prevent the bot from responding to every message in busy channels. Try mentioning the bot by name and see if it replies. Full configuration options are in the requireMention guide.

Channel permissions. If the bot can't read or write in the channel, it's silent even with everything else configured correctly. Check the channel's permission settings for the bot's role. The Discord permissions guide walks through this.

One more thing: if the server was recently re-added after the bot was kicked, the guild ID is the same but the pairing resets. The bot needs re-approval even if it was previously approved.

FAQ

My OpenClaw Discord bot is online but shows "playing" status instead of responding. What's wrong?

The "playing" status is the default presence OpenClaw sets for Discord bots. It doesn't indicate a problem with message handling. If the bot looks online but doesn't respond to messages, the status display isn't the issue. Check the logs for drop lines as described in the diagnosis section. The most common causes are an unapproved guild pairing or a missing Server Members Intent. To change the status itself, update the presence block in your OpenClaw config:

{
  "channels": {
    "discord": {
      "accounts": {
        "default": {
          "presence": {
            "status": "online",
            "activities": [
              {
                "name": "with AI",
                "type": "WATCHING"
              }
            ]
          }
        }
      }
    }
  }
}

Restart the gateway after updating config. Type options are PLAYING, WATCHING, LISTENING, and STREAMING.

The bot lags and replies 10-20 seconds late on Discord. Why?

Discord rate limits are the most likely cause. If the bot or the channel is sending messages quickly, Discord throttles outbound replies. OpenClaw respects these limits automatically, which means it queues replies and sends them when Discord allows. You'll see this in active channels during peak usage. It's a Discord platform constraint, not something configurable in OpenClaw.

A second cause is AI provider latency. If your bot uses an API like Anthropic or OpenAI, the reply time includes the time it takes that API to generate a response. High-load periods on the provider side can add several seconds. Check your provider's status page if this happens consistently.

I approved the pairing but my OpenClaw Discord bot still doesn't respond. What else could it be?

Check these in order:

1. Guild allowlist. If your guilds config array isn't empty, the server ID needs to be listed there. An approved pairing doesn't override an allowlist restriction.
2. requireMention. It's enabled by default. The bot only responds when you mention it by name. Try @YourBotName hello and see if that gets a reply.
3. Server Members Intent. Check the Discord developer portal. A missing intent causes the bot to connect cleanly but ignore messages.
4. Channel permissions. If the bot doesn't have "Send Messages" or "Read Message History" in that specific channel, it stays silent even with server-level permissions set. See the permissions guide for the full checklist.

Does my OpenClaw Discord bot need administrator permission to respond?

No. Administrator permission is not required for basic message handling. The minimum permissions OpenClaw needs to receive and reply to messages are: View Channel, Send Messages, Read Message History, and Embed Links. Administrator permission gives the bot access to every action in the server, including sensitive ones like managing roles and kicking members. Don't grant it unless a specific feature requires it. If you're seeing permission errors despite having those four permissions set, check that the bot's role is positioned correctly in the server's role hierarchy. See the Discord permissions guide for role position details.

Changelog

• 2026-03-07: Created (split from fix-openclaw-discord-errors)