openclaw - 💡(How to fix) Fix Docs mention Dreaming config/commands, but 2026.4.2 local build does not expose them [2 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#61421Fetched 2026-04-08 02:58:51
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Timeline (top)
subscribed ×4commented ×2unsubscribed ×1

The public OpenClaw docs describe experimental Dreaming support for memory-core, including config at plugins.entries.memory-core.config.dreaming.mode and CLI/chat surfaces like openclaw memory promote / /dreaming.

However, on a local install of OpenClaw 2026.4.2, the installed CLI/docs/plugin schema do not appear to expose those capabilities yet. Trying to apply the documented config makes openclaw.json invalid.

Root Cause

The public OpenClaw docs describe experimental Dreaming support for memory-core, including config at plugins.entries.memory-core.config.dreaming.mode and CLI/chat surfaces like openclaw memory promote / /dreaming.

However, on a local install of OpenClaw 2026.4.2, the installed CLI/docs/plugin schema do not appear to expose those capabilities yet. Trying to apply the documented config makes openclaw.json invalid.

Code Example

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "mode": "core"
          }
        }
      }
    }
  }
}

---

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
  - plugins.entries.memory-core.config: invalid config: must NOT have additional properties

---

/opt/homebrew/lib/node_modules/openclaw/dist/extensions/memory-core/openclaw.plugin.json

---

{
  "id": "memory-core",
  "kind": "memory",
  "configSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {}
  }
}

---

openclaw memory --help

---

/opt/homebrew/lib/node_modules/openclaw/docs/cli/memory.md
RAW_BUFFERClick to expand / collapse

Summary

The public OpenClaw docs describe experimental Dreaming support for memory-core, including config at plugins.entries.memory-core.config.dreaming.mode and CLI/chat surfaces like openclaw memory promote / /dreaming.

However, on a local install of OpenClaw 2026.4.2, the installed CLI/docs/plugin schema do not appear to expose those capabilities yet. Trying to apply the documented config makes openclaw.json invalid.

Environment

  • OpenClaw: 2026.4.2 (d74a122)
  • OS: macOS arm64
  • Memory plugin active: memory-core

What I expected

Based on the docs, I expected this config to be valid:

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "mode": "core"
          }
        }
      }
    }
  }
}

And I expected corresponding Dreaming surfaces to exist, such as:

  • openclaw memory promote ...
  • /dreaming ...
  • local CLI/docs reflecting the feature

What actually happens

1. Config becomes invalid

Adding the documented plugins.entries.memory-core.config.dreaming.mode config causes validation failure:

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
  - plugins.entries.memory-core.config: invalid config: must NOT have additional properties

2. Bundled plugin schema appears empty

The bundled plugin manifest at:

/opt/homebrew/lib/node_modules/openclaw/dist/extensions/memory-core/openclaw.plugin.json

contains:

{
  "id": "memory-core",
  "kind": "memory",
  "configSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {}
  }
}

So the installed build appears to accept no memory-core config keys at all.

3. Installed CLI/docs do not expose the documented Dreaming commands

On this install:

openclaw memory --help

only shows:

  • index
  • search
  • status

No promote subcommand is listed.

Also the bundled local docs at:

/opt/homebrew/lib/node_modules/openclaw/docs/cli/memory.md

do not mention Dreaming/promote, while the public docs do.

Repro steps

  1. Install/run OpenClaw 2026.4.2.
  2. Confirm memory-core is active via openclaw status / openclaw memory status --deep --json.
  3. Add the documented config under plugins.entries.memory-core.config.dreaming.mode.
  4. Run openclaw status or openclaw config get ....
  5. Observe config validation failure.
  6. Run openclaw memory --help.
  7. Observe there is no promote subcommand.

Why this is confusing

Right now the public docs strongly imply that Dreaming is available in this release line, but the local installed build/docs/schema suggest otherwise. It is hard to tell whether this is:

  • a docs/version skew issue
  • a packaging issue
  • or a feature that is only partially shipped in 2026.4.2

Request

Could you clarify which of these is true?

  1. Dreaming is not actually available in 2026.4.2 yet, and the public docs are ahead of the release.
  2. Dreaming is available, but the config path / enablement path is different in the shipped build.
  3. The package is missing the expected schema/CLI/docs wiring.

If helpful, I can also provide the exact local command outputs we saw during debugging.

extent analysis

TL;DR

The most likely fix is to wait for a future version of OpenClaw where the Dreaming feature is fully implemented and documented, as the current version 2026.4.2 does not support it despite the public documentation suggesting otherwise.

Guidance

  • Verify the version of OpenClaw and check the official documentation for any notes on the Dreaming feature's availability in that version.
  • Compare the local documentation and CLI output with the public documentation to identify any discrepancies.
  • Consider reaching out to the OpenClaw support team or community forums for clarification on the feature's status and any potential workarounds.
  • If the feature is not available in the current version, consider upgrading to a newer version when it becomes available, assuming the feature is implemented in a later release.

Notes

The issue seems to be a documentation and version skew problem, where the public documentation is ahead of the current release. Without more information about the development roadmap or release notes, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Wait for a future version of OpenClaw where the Dreaming feature is fully implemented and documented. This approach avoids potential configuration issues or misunderstandings due to the discrepancy between the public documentation and the current version's capabilities.

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