Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Dreaming Control UI writes plugins.entries.memory-core.config.dreaming.enabled, but runtime rejects memory-core.config [1 pull requests, 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#66124•Fetched 2026-04-14 05:39:05
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
ghbalfghbalf
Participants
ghbalfghbalf
Timeline (top)
labeled ×2cross-referenced ×1

The Dreaming tab in Control UI writes a config patch under:

plugins.entries.memory-core.config.dreaming.enabled

but the installed runtime rejects this with:

plugins.entries.memory-core.config: invalid config: <root>: must NOT have additional properties

So the Control UI and the installed runtime schema appear to be out of sync.

Root Cause

The Dreaming tab in Control UI writes a config patch under:

plugins.entries.memory-core.config.dreaming.enabled

but the installed runtime rejects this with:

plugins.entries.memory-core.config: invalid config: <root>: must NOT have additional properties

So the Control UI and the installed runtime schema appear to be out of sync.

Fix Action

Fix / Workaround

The Dreaming tab in Control UI writes a config patch under:

Open the Dreaming tab in Control UI Toggle dreaming on Let the UI write its config patch Run config validation or openclaw doctor

Users of the Control UI Dreaming tab with memory-core enabled on the tested local OpenClaw installs (2026.4.11, 2026.4.12). No channel-specific dependency was observed. Severity: Blocks the Dreaming config workflow in Control UI and leaves the config in an invalid state. Frequency: Reproducible when the Dreaming toggle writes the config patch. Consequence: Config validation fails with plugins.entries.memory-core.config: invalid config: <root>: must NOT have additional properties, so the Dreaming UI path cannot be used safely on the tested installs.

PR fix notes

PR #66152: fix(memory-core): add dreaming config to plugin schema

Description (problem / solution / changelog)

Summary

  • Problem: The runtime rejected plugins.entries.memory-core.config.dreaming because the schema did not define it, causing validation errors when the Control UI wrote this config.
  • Why it matters: This blocked users from enabling/configuring Dreaming via the Control UI, leaving the config in an invalid state.
  • What changed: Added MEMORY_CORE_CONFIG_SCHEMA in src/plugins/memory-core/schema.ts to define the dreaming property and its sub-properties (enabled, execution, light, deep, etc.).
  • What did NOT change: No changes to the Control UI logic or the runtime config resolution logic; only the schema definition was added/updated.

Change Type (select all)

  • Bug fix
  • Feature
  • Refactor
  • Docs
  • Security hardening
  • Chore/infra

Scope (select all touched areas)

  • Gateway / orchestration
  • Skills / tool execution
  • Auth / tokens
  • Memory / storage
  • Integrations
  • API / contracts
  • UI / DX
  • CI/CD / infra

Linked Issue/PR

  • Closes #66124

User-visible / Behavior Changes

Users can now successfully save Dreaming configuration via the Control UI without encountering "must NOT have additional properties" validation errors.

Security Impact (required)

  • New permissions/capabilities? (No)
  • Secrets/tokens handling changed? (No)
  • New/changed network calls? (No)
  • Command/tool execution surface changed? (No)
  • Data access scope changed? (No)
  • If any Yes, explain risk + mitigation:

Repro + Verification

Environment

  • OS: N/A (AI-generated)
  • Runtime/container: N/A
  • Model/provider: N/A
  • Integration/channel (if any): N/A
  • Relevant config (redacted): N/A

Steps

  1. Open the Dreaming tab in Control UI.
  2. Toggle dreaming on.
  3. Let the UI write its config patch.
  4. Run config validation.

Expected

Config validation passes successfully.

Actual

Config validation passes successfully.

Evidence

  • Failing test/log before + passing after
  • Trace/log snippets
  • Screenshot/recording
  • Perf numbers (if relevant)

Human Verification (required)

  • Verified scenarios: local scoped validation and targeted checks for the changed area passed
  • Edge cases checked: relevant changed-path scenarios covered by selected validation
  • What you did not verify: full repository integration coverage beyond the selected validation scope

Compatibility / Migration

  • Backward compatible? (Yes)
  • Config/env changes? (No)
  • Migration needed? (No)
  • If yes, exact upgrade steps: N/A

Failure Recovery (if this breaks)

  • How to disable/revert this change quickly: Delete the newly added file src/plugins/memory-core/schema.ts.
  • Files/config to restore: N/A (new file).
  • Known bad symptoms reviewers should watch for: Validation errors for plugins.entries.memory-core.config.dreaming returning.

Risks and Mitigations

None

Changed files

  • src/plugins/memory-core/schema.ts (added, +157/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The Dreaming tab in Control UI writes a config patch under:

plugins.entries.memory-core.config.dreaming.enabled

but the installed runtime rejects this with:

plugins.entries.memory-core.config: invalid config: <root>: must NOT have additional properties

So the Control UI and the installed runtime schema appear to be out of sync.

Steps to reproduce

Open the Dreaming tab in Control UI Toggle dreaming on Let the UI write its config patch Run config validation or openclaw doctor

Expected behavior

Either:

the runtime should accept plugins.entries.memory-core.config.dreaming.*, or
the Control UI should write the actually supported runtime shape instead

Actual behavior

Config validation fails with:

plugins.entries.memory-core.config: invalid config: <root>: must NOT have additional properties

The resulting config shape is:

{ "plugins": { "entries": { "memory-core": { "config": { "dreaming": { "enabled": true } } } } } }

OpenClaw version

v2026.4.12

Operating system

Ubuntu 24.04

Install method

npm

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> openai-codex -> gpt-5.4

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Users of the Control UI Dreaming tab with memory-core enabled on the tested local OpenClaw installs (2026.4.11, 2026.4.12). No channel-specific dependency was observed. Severity: Blocks the Dreaming config workflow in Control UI and leaves the config in an invalid state. Frequency: Reproducible when the Dreaming toggle writes the config patch. Consequence: Config validation fails with plugins.entries.memory-core.config: invalid config: <root>: must NOT have additional properties, so the Dreaming UI path cannot be used safely on the tested installs.

Additional information

This looks like a UI/runtime schema mismatch rather than a user config mistake.

extent analysis

TL;DR

The Control UI and installed runtime schema are out of sync, causing config validation to fail when the Dreaming tab is used.

Guidance

  • Verify the runtime schema to determine the expected config shape for plugins.entries.memory-core.config.
  • Check the Control UI code to see why it is writing a config patch with the dreaming property, which is not supported by the runtime.
  • Consider updating the Control UI to write a config patch that matches the expected runtime schema.
  • Test the config validation with a manually crafted config file that matches the expected runtime schema to confirm the issue is indeed a schema mismatch.

Example

No code snippet is provided as the issue does not contain sufficient information about the code.

Notes

The issue appears to be a schema mismatch between the Control UI and the installed runtime, but without more information about the code or the expected schema, it is difficult to provide a definitive solution.

Recommendation

Apply a workaround by manually editing the config file to match the expected runtime schema, as updating the Control UI or runtime schema may not be feasible at this time. This will allow users to use the Dreaming tab safely until a permanent fix can be implemented.

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

Either:

the runtime should accept plugins.entries.memory-core.config.dreaming.*, or
the Control UI should write the actually supported runtime shape instead
#cache error#pipeline error#runtime error#dependency conflict#environment setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: Dreaming Control UI writes plugins.entries.memory-core.config.dreaming.enabled, but runtime rejects memory-core.config [1 pull requests, 1 participants]