Fix: Discord "Failed to Resolve Application ID" in OpenClaw

TL;DR: You put the bot token where the application ID should go (or vice versa). They're different things.

The Error

channel exited: Failed to resolve Discord application id

You might also see:

Discord: invalid application id — could not authenticate

Error: Failed to login to Discord — check your application ID and bot token

Why This Happens

Discord has a confusing setup with multiple credentials that look similar:

• Application ID — A numeric ID like 1234567890123456789 (found on the General Information page)
• Bot Token — A long string like MTIzNDU2Nzg5MDEy.GH8kLw.abc123... (found on the Bot page)
• Client Secret — Another long string (found on OAuth2 page — you don't need this)

The most common mistake is putting the bot token in the application ID field, or leaving the application ID blank and only configuring the token. OpenClaw needs both, and they go in different config fields.

(GitHub #2203)

How to Fix It

Step 1: Get your credentials from Discord Developer Portal

Go to discord.com/developers/applications and select your bot's application.

Get the Application ID:

1. Click General Information in the left sidebar
2. Copy the Application ID (it's a number)

Get the Bot Token:

1. Click Bot in the left sidebar
2. Click Reset Token (or Copy if you see it)
3. Copy the token (it's a long encoded string)

⚠️ If you've never created a bot user, click Add Bot first.

Step 2: Update your OpenClaw config

Edit your clawdbot.json:

{
  "channels": {
    "discord": {
      "applicationId": "1234567890123456789",
      "token": "MTIzNDU2Nzg5MDEy.GH8kLw.abc123def456..."
    }
  }
}

Important:

• applicationId = the numeric ID from General Information
• token = the bot token from the Bot page
• Don't mix them up. Don't put the token in the applicationId field.

Step 3: Make sure your bot has the right permissions

Back in the Discord Developer Portal:

1. Go to Bot in the left sidebar
2. Under Privileged Gateway Intents, enable:
   • ✅ Message Content Intent
   • ✅ Server Members Intent (if your bot needs to see member lists)
3. Click Save Changes

Step 4: Invite the bot to your server

If you haven't already, generate an invite link:

1. Go to OAuth2 → URL Generator
2. Under Scopes, select bot
3. Under Bot Permissions, select at minimum:
   • Send Messages
   • Read Message History
   • Use Slash Commands
4. Copy the generated URL and open it in your browser
5. Select your server and authorize

Step 5: Restart and test

openclaw gateway restart
openclaw channel discord status

Send a message in the channel where your bot is — you should get a response.

Full setup from scratch (if you don't have a bot yet)

If you're starting fresh:

# 1. Go to https://discord.com/developers/applications
# 2. Click "New Application" → name it → Create
# 3. Copy the Application ID from General Information
# 4. Go to Bot → Add Bot → Copy the token
# 5. Go to Bot → Enable "Message Content Intent"
# 6. Go to OAuth2 → URL Generator → select "bot" scope
# 7. Select permissions → Copy URL → open in browser → add to server

Then configure OpenClaw:

{
  "channels": {
    "discord": {
      "applicationId": "YOUR_APPLICATION_ID_HERE",
      "token": "YOUR_BOT_TOKEN_HERE"
    }
  }
}

openclaw gateway restart

How to Prevent It

• Label your credentials when you save them. "Discord App ID: 123..." and "Discord Bot Token: MTI..." so you don't mix them up later.
• Never regenerate your bot token unless you need to. If you do, update your OpenClaw config immediately — the old token is instantly invalid.
• Double-check the field names in your config. applicationId ≠ token. It seems obvious, but this mistake fills GitHub issues.

The Easy Way

lobsterfarm is a managed hosting service for OpenClaw — deployment, updates, and support handled for you.

Get started with lobsterfarm →