openclaw - 💡(How to fix) Fix Config validation error after removing bundled plugins from allowlist (RESOLVED) [4 comments, 2 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#68932Fetched 2026-04-20 12:04:18
View on GitHub
Comments
4
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×4closed ×1renamed ×1

Error Message

Failed to start CLI: Error: Invalid config at /Users/andy51/.openclaw/openclaw.json:

Fix Action

Workaround

Restore bundled plugins to plugins.allow list even though they trigger security audit warnings.

Code Example

Failed to start CLI: Error: Invalid config at /Users/andy51/.openclaw/openclaw.json:
RAW_BUFFERClick to expand / collapse

Error Details

After removing bundled plugins (deepseek, brave, kimi, memory-core) from plugins.allow, OpenClaw CLI fails to start with:

Failed to start CLI: Error: Invalid config at /Users/andy51/.openclaw/openclaw.json:

Environment

  • OpenClaw version: 2026.4.15
  • OS: macOS 26.4.1 (arm64)
  • Node: 25.8.2

Steps to Reproduce

  1. Original plugins.allow contained: ["openclaw-lark", "deepseek", "brave", "kimi", "memory-core"]
  2. Changed to: ["openclaw-lark"] (only non-bundled plugin)
  3. Run any openclaw command → Config validation error

Expected Behavior

Bundled plugins should not need to be in plugins.allow to avoid the security warning about "phantom entries".

Actual Behavior

Removing them causes config validation to fail entirely.

Workaround

Restore bundled plugins to plugins.allow list even though they trigger security audit warnings.

Questions

  1. What is the correct way to handle bundled plugins in plugins.allow?
  2. Should bundled plugins be excluded from the "phantom entry" security check?
  3. Is there a different config schema for bundled vs installed plugins?

/cc @openclaw/maintainers

extent analysis

TL;DR

The most likely fix is to restore the bundled plugins to the plugins.allow list or wait for an update that properly handles bundled plugins in the configuration validation.

Guidance

  • Verify that the plugins.allow list only contains the required non-bundled plugin (openclaw-lark) and test if the issue persists with the bundled plugins removed.
  • Check the OpenClaw documentation for any specific instructions on handling bundled plugins in the plugins.allow list.
  • Consider reaching out to the OpenClaw maintainers (@openclaw/maintainers) for further guidance on the correct configuration schema for bundled vs installed plugins.
  • Test the workaround of restoring the bundled plugins to the plugins.allow list to ensure the CLI starts without errors.

Example

No code snippet is provided as the issue is related to configuration and not code.

Notes

The issue seems to be related to a configuration validation error when bundled plugins are removed from the plugins.allow list. The exact cause and solution may depend on the specific OpenClaw version and configuration.

Recommendation

Apply the workaround of restoring the bundled plugins to the plugins.allow list, as it is the most straightforward way to resolve the issue and allow the OpenClaw CLI to start without errors.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING