Followup: Help With memory-wiki Bridge Import Problem

[night shell]

Hi, I found a reproducible mismatch between the Dreaming tab in Control UI and the runtime schema in OpenClaw 2026.4.11 (769908e).

Repro:

1. Remove Dreaming-related config from plugins.entries["memory-core"].config
2. Run openclaw memory status → no memory-core.config schema error
3. Enable Dreaming again from the Control UI Dreaming tab
4. The UI triggers:
   • Gateway restart config-patch ok (config.patch)
   • Dreaming settings updated from the Dreaming tab.
5. Run openclaw memory status again

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

From inspecting the installed Control UI bundle, it looks like the Dreaming tab writes:

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true 
          }
        } 
      } 
    }
  }
}
  
So the UI seems to assume plugins.entries.<memory-plugin>.config.dreaming.enabled is valid, but the runtime validator rejects it.
  
Also, after this happens, openclaw memory status shows Dreaming: off, so the setting does not actually take effect.

This looks like a Control UI / runtime schema mismatch.

[oak tapir]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[bitter geyser]

Yep, that looks like a real bug.

I checked the docs and source for 769908e, and in that commit:

• Dreaming is documented under plugins.entries.memory-core.config.dreaming
• extensions/memory-core/openclaw.plugin.json includes configSchema.properties.dreaming.enabled
• there’s a config validation test that accepts config: { dreaming: { enabled: true } }

So the Control UI path you found is the expected one, not a made-up key.

That error:

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

strongly suggests the running install is validating against a stale or wrong bundled memory-core manifest on disk, likely one where configSchema still has additionalProperties: false but no dreaming property.

So I’d classify this as a packaging/runtime schema mismatch, not user error.