openclaw - ✅(Solved) Fix dreaming CLI: plugins.allow false-positive plugin not found warning [2 pull requests, 1 participants]

Wanxian-Liu · 2026-04-10T08:18:43Z

[openclaw] PR 64221: fix config : clarify dreaming allowlist warnings - Repository: openclaw/openclaw - Author: OwenYWT - State: closed | merged: False - Link:… # PR #64221: fix(config): clarify dreaming allowlist warnings - Repository: openclaw/openclaw - Author: OwenYWT - State: closed | merged: False - Link: https://github.com/openclaw/openclaw/pull/64221 ## Description (problem / solution / changelog) Addresses #64191 ## Summary - stop reporting `dreaming` as a stale unknown plugin id in `plugins.allow` - replace that warning with explicit guidance that `dreaming` is a memory-core command, not a plugin id - add validation coverage for the guided warning path ## Test Plan - [x] `pnpm --dir /Users/wentao/Desktop/openclaw exec vitest run src/plugins/config-policy.test.ts src/plugins/loader.test.ts src/config/config.plugin-validation.test.ts src/agents/skills/workspace.load-order.test.ts` - [x] `NODE_OPTIONS=--max-old-space-size=8192 pnpm --dir /Users/wentao/Desktop/openclaw exec tsc --noEmit --pretty false` ## Changed files - `extensions/comfy/image-generation-provider.test.ts` (modified, +26/-0) - `extensions/comfy/music-generation-provider.test.ts` (modified, +67/-0) - `extensions/comfy/video-generation-provider.test.ts` (modified, +28/-0) - `extensions/comfy/workflow-runtime.ts` (modified, +5/-2) - `extensions/memory-core/src/memory/index.test.ts` (modified, +6/-0) - `extensions/memory-core/src/memory/provider-adapters.ts` (modified, +39/-1) - `extensions/whatsapp/src/session.runtime.ts` (modified, +1/-0) - `extensions/whatsapp/src/session.test.ts` (modified, +67/-27) - `extensions/whatsapp/src/session.ts` (modified, +33/-1) - `src/agents/skills/workspace.load-order.test.ts` (added, +48/-0) - `src/agents/skills/workspace.ts` (modified, +25/-23) - `src/agents/tools/sessions-announce-target.ts` (modified, +15/-1) - `src/agents/tools/sessions-helpers.ts` (modified, +2/-0) - `src/agents/tools/sessions.test.ts` (modified, +27/-0) - `src/config/config.plugin-validation.test.ts` (modified, +25/-0) - `src/config/validation.ts` (modified, +8/-0) - `src/infra/outbound/message-action-params.test.ts` (modified, +36/-1) - `src/infra/outbound/message-action-params.ts` (modified, +7/-2) - `src/memory-host-sdk/engine-embeddings.ts` (modified, +4/-0) - `src/plugins/config-normalization-shared.ts` (modified, +3/-0) - `src/plugins/config-policy.test.ts` (modified, +12/-0) - `src/plugins/loader.test.ts` (modified, +3/-1) - `src/plugins/loader.ts` (modified, +1/-1) - `test/mocks/baileys.ts` (modified, +8/-0) --- # PR #64242: fix(config): give actionable guidance when command names are used in plugins.allow (#64191) - Repository: openclaw/openclaw - Author: feiskyer - State: closed | merged: True - Link: https://github.com/openclaw/openclaw/pull/64242 ## Description (problem / solution / changelog) ## Summary - **Problem:** Putting `"dreaming"` in `plugins.allow` causes a "plugin not found" warning, and running `openclaw dreaming` from CLI misleadingly tells users to add `"dreaming"` to `plugins.allow` — creating a circular trap where neither path works. - **Why it matters:** Users cannot discover that `/dreaming` is a runtime slash command from `memory-core`, not a standalone plugin or CLI command. The error messages actively mislead them. - **What changed:** Added a command-name-to-plugin-id map so both validation and CLI resolution give actionable guidance pointing users to the correct plugin id (`memory-core`) and the correct usage (`/dreaming` in chat or `openclaw memory` on CLI). - **What did NOT change:** No new features, no behavioral changes to dreaming itself, no changes to how `plugins.allow` enforcement works. Generic "plugin not found" handling for truly unknown ids is untouched. ## Change Type (select all) - [x] Bug fix - [ ] Feature - [ ] Refactor required for the fix - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [x] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [x] Memory / storage - [ ] Integrations - [ ] API / contracts - [x] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes #64191 - [x] This PR fixes a bug or regression ## Root Cause (if applicable) - **Root cause:** `dreaming` is a runtime slash command registered by the `memory-core` plugin via `api.registerCommand()`, but both config validation and CLI command resolution treat unrecognized names as plugin ids. Neither path knows that some command names map to parent plugins. - **Missing detection / guardrail:** No mapping existed between well-known runtime command names and their parent plugin ids. - **Contributing context:** The `memory-core` plugin registers CLI commands under `memory` (via `api.registerCli()`) but its slash command under `dreaming` (via `api.registerCommand()`). The naming mismatch between the CLI surface (`memory`) and the slash command (`dreaming`) makes this confusing. ## Regression Test Plan (if applicable) - Coverage level that should have caught t

openclaw2026-04-10 08:18:43

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#64191•Fetched 2026-04-11 06:15:58

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Wanxian-Liu

Participants

Wanxian-Liu

Timeline (top)

referenced ×6cross-referenced ×3closed ×1

Code Example

"plugins": {
  "allow": ["dreaming"],
  "entries": {
    "memory-core": {
      "config": {
        "dreaming": {
          "enabled": true
        }
      }
    }
  }
}

---

plugins.allow: plugin not found: dreaming (stale config entry ignored; remove it from plugins config)

RAW_BUFFERClick to expand / collapse

Bug: dreaming CLI - plugins.allow false-positive warning

问题：openclaw dreaming [status|on|off] CLI 命令需要在 plugins.allow 里加 "dreaming"，但加了之后反而报 "plugin not found" 被当作无效配置忽略。

配置：

"plugins": {
  "allow": ["dreaming"],
  "entries": {
    "memory-core": {
      "config": {
        "dreaming": {
          "enabled": true
        }
      }
    }
  }
}

错误信息：

plugins.allow: plugin not found: dreaming (stale config entry ignored; remove it from plugins config)

根因：dreaming 不是独立插件，是 memory-core 的内部功能，但 CLI 命令的注册机制却要求它必须在 plugins.allow 里。

现状：memory-core 的 dreaming 功能在 cron 调度下正常运行，但 /dreaming on/off/status 这些 CLI 命令完全无法使用。

建议修复：文档明确说明不应该把 dreaming 加到 plugins.allow，或者把 dreaming 注册为真正的插件 ID。

extent analysis

TL;DR

Remove "dreaming" from the plugins.allow configuration to prevent the false-positive warning and allow the memory-core dreaming functionality to work as expected.

Guidance

Verify that the dreaming functionality is indeed part of the memory-core plugin and not a separate plugin by checking the plugin's documentation or code.
Remove "dreaming" from the plugins.allow array in the configuration file to prevent the warning and potential configuration issues.
Check the memory-core plugin's configuration to ensure that the dreaming feature is enabled and properly configured.
Test the memory-core dreaming functionality after removing "dreaming" from plugins.allow to ensure it works as expected.

Example

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

Notes

The issue seems to be caused by a mismatch between the plugin registration mechanism and the actual implementation of the dreaming feature within the memory-core plugin. Removing "dreaming" from plugins.allow should resolve the warning and allow the feature to work, but it's essential to verify the plugin's documentation and configuration to ensure correct functionality.

Recommendation

Apply workaround: Remove "dreaming" from plugins.allow to prevent the false-positive warning and allow the memory-core dreaming functionality to work as expected. This is because the dreaming feature is not a separate plugin, but rather an internal functionality of the memory-core 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?

#permission error #memory optimization #batch processing #GPU compatibility #latency issue

Still need to ship something?

×6

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

openclaw - ✅(Solved) Fix dreaming CLI: plugins.allow false-positive plugin not found warning [2 pull requests, 1 participants]

Recommended Tools

GitHub issue graph ai analysis

Fix Action

Fixed

PR fix notes

PR #64221: fix(config): clarify dreaming allowlist warnings

Description (problem / solution / changelog)

Summary

Test Plan

Changed files

PR #64242: fix(config): give actionable guidance when command names are used in plugins.allow (#64191)

Description (problem / solution / changelog)

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Root Cause (if applicable)

Regression Test Plan (if applicable)

Security Impact

Human Verification (required)

Review Conversations

Compatibility / Migration

Risks and Mitigations