Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bundled CLI command 'dreaming' blocked by plugins.allow validation conflict [1 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#63501•Fetched 2026-04-09 07:53:00
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
yysf1949yysf1949
Participants
yysf1949yysf1949
Timeline (top)
subscribed ×1

Error Message

  • Error message: "Add 'dreaming' to plugins.allow if you want that bundled plugin CLI surface"

Root Cause

  1. CLI Registration Logic (run-main-GjF7YCnf.js:357):

    • Checks if plugins.allow.includes("dreaming") to enable the command
    • Error message: "Add 'dreaming' to plugins.allow if you want that bundled plugin CLI surface"

  2. Config Validation Logic (loader-CVkGO8jl.js):

    • Validates that all entries in plugins.allow must be known plugin IDs
    • "dreaming" is not a standalone plugin ID, so it's marked as "stale config entry ignored"
    • Warning: "plugin not found: dreaming (stale config entry ignored; remove it from plugins config)"

  3. Result: CLI checks against the validated config where "dreaming" has been removed, so the command remains unavailable.

Code Example

{
  "plugins": {
    "allow": ["dreaming", "memory-core", "openclaw-lark", ...],
    "entries": {
      "memory-core": {
        "enabled": true,
        "config": {
          "dreaming": {
            "enabled": true,
            "frequency": "0 3 * * *"
          }
        }
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Problem Summary

The bundled CLI command openclaw dreaming is unavailable due to a design conflict between CLI command registration and configuration validation.

Root Cause Analysis

  1. CLI Registration Logic (run-main-GjF7YCnf.js:357):

    • Checks if plugins.allow.includes("dreaming") to enable the command
    • Error message: "Add 'dreaming' to plugins.allow if you want that bundled plugin CLI surface"

  2. Config Validation Logic (loader-CVkGO8jl.js):

    • Validates that all entries in plugins.allow must be known plugin IDs
    • "dreaming" is not a standalone plugin ID, so it's marked as "stale config entry ignored"
    • Warning: "plugin not found: dreaming (stale config entry ignored; remove it from plugins config)"

  3. Result: CLI checks against the validated config where "dreaming" has been removed, so the command remains unavailable.

Current Configuration

{
  "plugins": {
    "allow": ["dreaming", "memory-core", "openclaw-lark", ...],
    "entries": {
      "memory-core": {
        "enabled": true,
        "config": {
          "dreaming": {
            "enabled": true,
            "frequency": "0 3 * * *"
          }
        }
      }
    }
  }
}

Expected Behavior

One of the following should work:

  1. plugins.allow accepts "dreaming" as a valid bundled CLI command identifier
  2. CLI registration uses the plugin ID ("memory-core") instead of command name ("dreaming") for allowlist checking
  3. Config validation recognizes bundled CLI command names as valid allowlist entries

Environment

  • OpenClaw version: 2026.4.8
  • Node.js: v22.22.1
  • OS: Linux 6.17.0-20-generic

Possible Solutions

OptionDescription
AModify CLI registration to check plugin ID instead of command name
BAdd "dreaming" as a virtual bundled plugin ID
CBypass plugins.allow check for bundled CLI commands

Related Code References

  • CLI check: dist/run-main-GjF7YCnf.js:357
  • Config validation: dist/loader-CVkGO8jl.js (plugin loading logic)
  • Memory-core plugin: dist/extensions/memory-core/index.js (registers "dreaming" command)

This appears to affect all bundled CLI commands that are registered by plugins but checked against plugins.allow by command name rather than plugin ID.

extent analysis

TL;DR

Modify the CLI registration logic to check the plugin ID instead of the command name for allowlist checking.

Guidance

  • Review the run-main-GjF7YCnf.js file at line 357 to understand the current CLI registration logic and consider modifying it to use plugin IDs.
  • Update the plugins.allow configuration to use the plugin ID ("memory-core") instead of the command name ("dreaming") for bundled CLI commands.
  • Investigate adding a virtual bundled plugin ID for "dreaming" as an alternative solution, but be cautious of potential implications on config validation.
  • Verify the fix by checking if the openclaw dreaming command becomes available after applying the changes.

Example

{
  "plugins": {
    "allow": ["memory-core", "openclaw-lark", ...],
    "entries": {
      "memory-core": {
        "enabled": true,
        "config": {
          "dreaming": {
            "enabled": true,
            "frequency": "0 3 * * *"
          }
        }
      }
    }
  }
}

Notes

The provided solution assumes that modifying the CLI registration logic or updating the plugins.allow configuration will resolve the issue. However, the actual implementation may vary depending on the specific requirements and constraints of the OpenClaw project.

Recommendation

Apply workaround by modifying the CLI registration logic to check plugin IDs instead of command names, as this approach seems to be the most straightforward and least invasive solution.

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…
#generation error#database connection#vector store#embedding generation#cache 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