openclaw - 💡(How to fix) Fix [Bug]: Upgrade to 2026.5.2 silently breaks Discord routing — installs.json records plugins as installed without fetching, and migration doesn't populate plugins.allow [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#77106Fetched 2026-05-05 05:52:05
View on GitHub
Comments
3
Participants
3
Timeline
5
Reactions
2
Author
Timeline (top)
commented ×3closed ×1labeled ×1

After upgrading from 2026.4.29 to 2026.5.2, the Discord channel plugin stopped loading; reproduced and confirmed by gateway logs showing the plugin missing from the active list and a plugins.allow is empty warning.

Error Message

Discord plugin is not loaded after the upgrade. Three Discord bot identities (default/sales/sandy) fail to start. Gateway log emits: plugins.allow is empty; discovered non-bundled plugins may auto-load: brave, codex, discord. Set plugins.allow to explicit trusted ids. Additionally, openclaw doctor fails with tools.web.search.provider: web_search provider is not available: brave (install or enable plugin "brave", then run openclaw doctor --fix), and openclaw plugins install is itself blocked by the same config-validation error. ▎ clear error message pointing at the cause.

Root Cause

After upgrading from 2026.4.29 to 2026.5.2, the Discord channel plugin stopped loading; reproduced and confirmed by gateway logs showing the plugin missing from the active list and a plugins.allow is empty warning.

Fix Action

Fix / Workaround

▎ Last known good: 2026.4.29. First known bad: 2026.5.2.
▎ Workaround sequence: ▎ 1. npm install --prefix ~/.openclaw/npm @openclaw/[email protected] ▎ @openclaw/[email protected] @openclaw/[email protected] --no-save
▎ --no-package-lock (the --no-save is critical — without listing every ▎ plugin, siblings are purged).
▎ 2. Add plugins.allow: ["brave","discord","openai","webhooks"] to config. ▎ 3. Restart gateway.

Code Example

Doctor output:                                                          
Config invalid                                                
File: ~/.openclaw/openclaw.json      
Problem:                                                                
- tools.web.search.provider: web_search provider is not available: 
  ▎ brave                                                                   
       (install or enable plugin "brave", then run openclaw doctor --fix)
Gateway log after upgrade restart:                                      
  ▎ http server listening (8 plugins: bonjour, browser, device-pair, 
  ▎ file-transfer,                                                          
  ▎   memory-core, phone-control, talk-voice, webhooks; 2.5s)               
  ▎ plugins.allow is empty; discovered non-bundled plugins may auto-load: 
  ▎ brave, codex,                                                           
  ▎   discord. Set plugins.allow to explicit trusted ids.         
   installs.json (excerpt):                                                
"discord": { "spec": "@openclaw/discord", "installPath":                
"/Users/.../npm/node_modules/@openclaw/discord", "version": 
"2026.5.2",                                                             
"installedAt": "2026-05-04T02:27:32.442Z" }                 
Filesystem at same time:                                                
  ▎ $ ls ~/.openclaw/npm/node_modules/@openclaw/                            
  ▎ discord                                                                 
  ▎ $ ls ~/.openclaw/npm/node_modules/@openclaw/brave-plugin                
  ▎ ls: ... No such file or directory
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading from 2026.4.29 to 2026.5.2, the Discord channel plugin stopped loading; reproduced and confirmed by gateway logs showing the plugin missing from the active list and a plugins.allow is empty warning.

Steps to reproduce

  1. On an existing 2026.4.29 install with Discord channels working, run openclaw update --yes. ▎ 2. After the package update completes, run openclaw gateway restart.
    ▎ 3. Observe the gateway log line http server listening (8 plugins: bonjour, browser, device-pair, file-transfer, memory-core, phone-control, talk-voice, webhooks; 2.5s) — discord is absent.
    ▎ 4. Try to message a Discord-bound agent — no reply.

Expected behavior

In 2026.4.29, the Discord plugin loaded automatically based on channels.discord.enabled: true and bot account tokens, and agents replied on all configured Discord accounts.

Actual behavior

Discord plugin is not loaded after the upgrade. Three Discord bot identities (default/sales/sandy) fail to start. Gateway log emits: plugins.allow is empty; discovered non-bundled plugins may auto-load: brave, codex, discord. Set plugins.allow to explicit trusted ids. Additionally, openclaw doctor fails with tools.web.search.provider: web_search provider is not available: brave (install or enable plugin "brave", then run openclaw doctor --fix), and openclaw plugins install is itself blocked by the same config-validation error.

OpenClaw version

026.5.2 (8b2a6e5)

Operating system

macOS 26.2 (arm64)

Install method

pnpm (global)

Model

openai-codex/gpt-5.5

Provider / routing chain

openclaw → discord channel plugin → agent

Additional provider/model setup details

Pre-upgrade ~/.openclaw/openclaw.json had plugins.entries.brave and channels.discord.enabled: true with three account tokens (default/sales/sandy). No plugins.allow field existed. After upgrade, ~/.openclaw/plugins/installs.json listed @openclaw/[email protected], @openclaw/[email protected], @openclaw/[email protected] with installedAt timestamps and integrity hashes, but ~/.openclaw/npm/node_modules/@openclaw/ contained only discord/.

Logs, screenshots, and evidence

Doctor output:                                                          
  ▎ Config invalid                                                
  ▎ File: ~/.openclaw/openclaw.json      
  ▎ Problem:                                                                
  ▎   - tools.web.search.provider: web_search provider is not available: 
  ▎ brave                                                                   
(install or enable plugin "brave", then run openclaw doctor --fix)
  ▎ Gateway log after upgrade restart:                                      
  ▎ http server listening (8 plugins: bonjour, browser, device-pair, 
  ▎ file-transfer,                                                          
  ▎   memory-core, phone-control, talk-voice, webhooks; 2.5s)               
  ▎ plugins.allow is empty; discovered non-bundled plugins may auto-load: 
  ▎ brave, codex,                                                           
  ▎   discord. Set plugins.allow to explicit trusted ids.         
  ▎ installs.json (excerpt):                                                
"discord": { "spec": "@openclaw/discord", "installPath":                
"/Users/.../npm/node_modules/@openclaw/discord", "version": 
"2026.5.2",                                                             
"installedAt": "2026-05-04T02:27:32.442Z" }                 
  ▎ Filesystem at same time:                                                
  ▎ $ ls ~/.openclaw/npm/node_modules/@openclaw/                            
  ▎ discord                                                                 
  ▎ $ ls ~/.openclaw/npm/node_modules/@openclaw/brave-plugin                
  ▎ ls: ... No such file or directory

Impact and severity

Affected: any user upgrading to 2026.5.2 with Discord channels (and
▎ likely any non-bundled channel plugin) configured, plus anyone with ▎ tools.web.search.provider: brave.
▎ Severity: High — silently breaks chat routing on a daily-driver, with no ▎ clear error message pointing at the cause.
▎ Frequency: 1/1 observed upgrade. ▎ Consequence: All Discord-routed agents (3 in my case) stop responding.
▎ Recovery required ~30 minutes of manual diagnosis and an undocumented
▎ npm install --prefix ... --no-save --no-package-lock invocation, plus
▎ hand-editing plugins.allow.

Additional information

▎ Last known good: 2026.4.29. First known bad: 2026.5.2.
▎ Workaround sequence: ▎ 1. npm install --prefix ~/.openclaw/npm @openclaw/[email protected] ▎ @openclaw/[email protected] @openclaw/[email protected] --no-save
▎ --no-package-lock (the --no-save is critical — without listing every ▎ plugin, siblings are purged).
▎ 2. Add plugins.allow: ["brave","discord","openai","webhooks"] to config. ▎ 3. Restart gateway.

extent analysis

TL;DR

The Discord channel plugin fails to load after upgrading to OpenClaw version 2026.5.2 due to an empty plugins.allow configuration, which can be resolved by installing required plugins and configuring plugins.allow explicitly.

Guidance

  1. Install missing plugins: Run npm install --prefix ~/.openclaw/npm @openclaw/[email protected] @openclaw/[email protected] @openclaw/[email protected] --no-save --no-package-lock to ensure all necessary plugins are installed.
  2. Configure plugins.allow: Add plugins.allow: ["brave","discord","openai","webhooks"] to your OpenClaw configuration file (~/.openclaw/openclaw.json) to explicitly allow the required plugins.
  3. Restart the gateway: After installing the plugins and updating the configuration, restart the OpenClaw gateway to apply the changes.
  4. Verify plugin installation: Check the ~/.openclaw/npm/node_modules/@openclaw/ directory to ensure that all required plugins (e.g., brave-plugin, codex, discord) are installed.

Example

No code snippet is necessary for this solution, as it involves configuration changes and plugin installation.

Notes

The provided workaround sequence has been tested and confirmed to resolve the issue. However, it is essential to note that this solution assumes the plugins.allow configuration is the primary cause of the problem. If issues persist, further investigation into the OpenClaw configuration and plugin compatibility may be necessary.

Recommendation

Apply the workaround by installing the required plugins and configuring plugins.allow explicitly, as this approach has been confirmed to resolve the issue in the given scenario.

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

In 2026.4.29, the Discord plugin loaded automatically based on channels.discord.enabled: true and bot account tokens, and agents replied on all configured Discord accounts.

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]: Upgrade to 2026.5.2 silently breaks Discord routing — installs.json records plugins as installed without fetching, and migration doesn't populate plugins.allow [3 comments, 3 participants]