openclaw - ✅(Solved) Fix [Bug]: Discord channel not loaded in 2026.5.4 (and beta.2/beta.3), works in beta.1 and 2026.4.29 [1 pull requests, 3 comments, 3 participants]

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…
GitHub stats
openclaw/openclaw#77930Fetched 2026-05-06 06:19:15
View on GitHub
Comments
3
Participants
3
Timeline
6
Reactions
2
Author
Timeline (top)
commented ×3labeled ×2cross-referenced ×1

Discord channel not loaded in 2026.5.4 (and beta.2/beta.3), works in beta.1 and 2026.4.29

Regression matrix:

  • 2026.4.29 → works
  • 2026.5.3-1 → broken
  • 2026.5.4-beta.1 → works
  • 2026.5.4-beta.2 → broken
  • 2026.5.4-beta.3 → broken
  • 2026.5.4 → broken

Root Cause

Discord channel not loaded in 2026.5.4 (and beta.2/beta.3), works in beta.1 and 2026.4.29

Regression matrix:

  • 2026.4.29 → works
  • 2026.5.3-1 → broken
  • 2026.5.4-beta.1 → works
  • 2026.5.4-beta.2 → broken
  • 2026.5.4-beta.3 → broken
  • 2026.5.4 → broken

Fix Action

Fixed

PR fix notes

PR #78090: docs: call out discord external plugin install

Description (problem / solution / changelog)

Summary

Documents the Discord external plugin install step in the Discord quick setup.

The root package/Docker image no longer bundles the Discord runtime by default. A config-only channels.discord block can therefore leave Docker/npm users with Discord missing from openclaw plugins list and no loaded Discord channel. The existing install/doctor machinery is fine; the quick setup was the dishonest part because it implied config alone was enough.

Changes

  • Add a Discord setup step for openclaw plugins install @openclaw/discord.
  • Explain that Docker/npm/package installs need the external plugin before gateway startup.
  • Add recovery hint for configured-but-missing Discord: openclaw doctor --fix or explicit install, then restart.

Testing

  • git diff --check — passed.
  • PATH="/tmp/openclaw-pnpm-shim:$PATH" node scripts/check-changed.mjs — passed docs-only gates.

Fixes #77930

Changed files

  • docs/channels/discord.md (modified, +15/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Discord channel not loaded in 2026.5.4 (and beta.2/beta.3), works in beta.1 and 2026.4.29

Regression matrix:

  • 2026.4.29 → works
  • 2026.5.3-1 → broken
  • 2026.5.4-beta.1 → works
  • 2026.5.4-beta.2 → broken
  • 2026.5.4-beta.3 → broken
  • 2026.5.4 → broken

Steps to reproduce

  • Configure channels.discord with valid tokens
  • Start container

Expected behavior

  • Discord plugin loads and appears in plugin list

Actual behavior

  • Plugin list shows: browser, device-pair, file-transfer, memory-core, phone-control, talk-voice
  • Discord missing entirely
  • No errors in logs

OpenClaw version

2026.5.4

Operating system

Ubuntu 24.04

Install method

docker

Model

All models

Provider / routing chain

N/A

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The Discord channel not loading in version 2026.5.4 may be due to a regression introduced between versions 2026.4.29 and 2026.5.3-1, suggesting a potential fix could involve reviewing changes made during this period.

Guidance

  • Review the changelog or commit history between 2026.4.29 and 2026.5.3-1 to identify potential changes that could affect the Discord plugin.
  • Verify that the channels.discord configuration is correctly set up and valid tokens are used, as this is a prerequisite for the Discord plugin to load.
  • Test the Discord plugin with the beta.1 version of 2026.5.4 to confirm if the issue is indeed version-specific and to isolate the problem further.
  • Consider comparing the plugin lists and configurations between a working version (like 2026.4.29 or 2026.5.4-beta.1) and a non-working version (like 2026.5.4) to identify any discrepancies.

Example

No specific code snippet can be provided without more details on the implementation, but checking the configuration and setup for the Discord channel, such as ensuring that channels.discord is properly configured with valid tokens, is a crucial step.

Notes

The lack of error logs suggests the issue might not be with the Discord plugin itself but rather with how it's being loaded or recognized by the system in version 2026.5.4. Further investigation into the loading mechanism of plugins between different versions could provide more insight.

Recommendation

Apply a workaround by using version 2026.5.4-beta.1 until the issue is resolved in later versions, as it is confirmed to work with the Discord plugin.

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…

FAQ

Expected behavior

  • Discord plugin loads and appears in plugin list

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 - ✅(Solved) Fix [Bug]: Discord channel not loaded in 2026.5.4 (and beta.2/beta.3), works in beta.1 and 2026.4.29 [1 pull requests, 3 comments, 3 participants]