Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: False-positive "plugins.allow is empty" warning in openclaw status (2026.4.5) [1 pull requests, 2 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#62049•Fetched 2026-04-08 03:09:44
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
1
Author
MWiegand133MWiegand133
Participants
BrennerSpearBrennerSpearMWiegand133MWiegand133superfat1988superfat1988
Timeline (top)
cross-referenced ×3commented ×2referenced ×2labeled ×1

openclaw status reports:

[plugins] plugins.allow is empty; discovered non-bundled plugins may auto-load...

even though plugins.allow is explicitly configured and enforced.

This appears to be a false-positive warning path in some CLI/status flows.

Root Cause

openclaw status reports:

[plugins] plugins.allow is empty; discovered non-bundled plugins may auto-load...

even though plugins.allow is explicitly configured and enforced.

This appears to be a false-positive warning path in some CLI/status flows.

Fix Action

Fixed

PR fix notes

PR #62106: fix(plugins): downgrade plugins.allow warning to info level

Description (problem / solution / changelog)

The warning was displayed during normal openclaw status commands, even when no plugins are being loaded. This caused confusion as it appeared even with intentional empty allowlist configurations.

Closes #62049

Changed files

  • src/plugins/loader.test.ts (modified, +2/-2)
  • src/plugins/loader.ts (modified, +2/-2)

Code Example

openclaw --version

---

openclaw config get plugins.allow

---

openclaw status

---

openclaw status --all

---
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Summary

openclaw status reports:

[plugins] plugins.allow is empty; discovered non-bundled plugins may auto-load...

even though plugins.allow is explicitly configured and enforced.

This appears to be a false-positive warning path in some CLI/status flows.

Environment

  • OpenClaw: 2026.4.5
  • OS: Ubuntu (systemd gateway)
  • Config path: ~/.openclaw/openclaw.json

Steps to reproduce

Repro matrix

  1. Confirm version:
openclaw --version
  1. Confirm allowlist is set:
openclaw config get plugins.allow

(If config get is unavailable in this build, inspect ~/.openclaw/openclaw.json directly)

  1. Run:
openclaw status

Observed: warning plugins.allow is empty...

  1. Run:
openclaw status --all

Observed: warning does not appear.

  1. Confirm allowlist is actually enforced: A command/plugin excluded by plugins.allow is blocked (for example CLI command availability changes when allowlist is restrictive).

Expected behavior

No plugins.allow is empty warning when allowlist is configured and actively enforced.

Actual behavior

Warning appears in openclaw status but not in openclaw status --all, despite the same configured allowlist.

OpenClaw version

2026.4.5

Operating system

Ubuntu 24.04.4 LTS

Install method

No response

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> openai-codex

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Notes / likely area

Warning originates from:

  • dist/loader-BkajlJCF.js
  • warnWhenAllowlistIsOpen(...)
  • warning emits only when normalized.allow.length === 0

This suggests at least one status/plugin loader path is resolving plugin config differently (or without the expected activation context), causing a false positive.

extent analysis

TL;DR

The issue can be mitigated by using the --all flag with the openclaw status command, which does not produce the false-positive warning.

Guidance

  • Verify that the plugins.allow configuration is correctly set by checking the output of openclaw config get plugins.allow or by inspecting the ~/.openclaw/openclaw.json file directly.
  • Run openclaw status --all instead of openclaw status to avoid the warning, as the issue seems to be specific to the default status command.
  • Investigate the difference in behavior between openclaw status and openclaw status --all to understand why the warning is not emitted in the latter case.
  • Check the code in dist/loader-BkajlJCF.js and the warnWhenAllowlistIsOpen function to see how the normalized.allow.length value is being determined and why it might be zero in the default status command.

Example

No code snippet is provided as the issue is more related to configuration and command-line usage.

Notes

The root cause of the issue seems to be related to how the plugin configuration is being loaded or resolved in different commands, but without more information about the code or the configuration, it's difficult to provide a more specific fix.

Recommendation

Apply workaround: using the --all flag with the openclaw status command is a viable temporary solution to avoid the false-positive warning until the underlying issue can be addressed.

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

No plugins.allow is empty warning when allowlist is configured and actively enforced.

#ssr#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

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

Back to top recommendations

TRENDING