Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Discord channel silently skipped during gateway startup

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…

Error Message

Gateway journal shows:

No Discord-related log entries despite channels.discord being configured and enabled.

Code Example

{
  "channels": {
    "discord": {
      "enabled": true,
      "token": "MTQ4NT... (valid 72-char token)",
      "groupPolicy": "allowlist",
      "guilds": { "*": {} },
      "allowFrom": ["discord:209451187286573056"],
      "dmPolicy": "allowlist",
      "streaming": { "mode": "off" }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Bug Description

OpenClaw gateway skips Discord channel initialization silently — no error, no Discord start log, bot never connects via gateway WebSocket.

Environment

  • OpenClaw v2026.5.7
  • Discord plugin loaded and enabled (confirmed via openclaw plugins list)
  • Bot token valid — verified via Discord REST API (curl -s -H "Authorization: Bot TOKEN" https://discord.com/api/v10/users/@me returns bot info)
  • Config appears correct — channels.discord has enabled:true, token, dmPolicy:allowlist, allowFrom with user ID

Config

{
  "channels": {
    "discord": {
      "enabled": true,
      "token": "MTQ4NT... (valid 72-char token)",
      "groupPolicy": "allowlist",
      "guilds": { "*": {} },
      "allowFrom": ["discord:209451187286573056"],
      "dmPolicy": "allowlist",
      "streaming": { "mode": "off" }
    }
  }
}

What Works

  • Direct REST API calls to Discord with the same token work fine
  • RSS cron job can post to Discord via direct HTTP calls using the same token
  • Bot shows as "OpenClaw_" in Discord's API
  • Plugin IS loaded: openclaw plugins list shows @openclaw/discord as enabled

What Doesn't Work

  • Gateway never attempts to start Discord channel
  • Logs show [gateway] starting channels and sidecars... then jumps straight to Telegram start — no Discord attempt at all
  • openclaw status only shows Telegram, no Discord entry
  • openclaw message send --channel discord returns "Channel is unavailable: discord"

Logs

Gateway journal shows:

No Discord-related log entries despite channels.discord being configured and enabled.

Additional Notes

  • Config change triggers "config change requires gateway restart (channels.discord)" correctly
  • Multiple restart attempts don't help
  • Tried: removing/re-adding discord config, adding accounts.default with explicit token, multiple restart cycles
  • Token verified working via direct REST call — bot username OpenClaw_ confirmed

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…
#api#ssr#installation#tensor shape#autograd error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug] Discord channel silently skipped during gateway startup