2026-04-24 10:16:25.312943+00:00Invalid config at /home/node/.openclaw/openclaw.json:\n- plugins.entries.memory-core.config: invalid config: must NOT have additional properties
2026-04-24 10:16:41.113265+00:00Config invalid
2026-04-24 10:16:41.115455+00:00File: ~/.openclaw/openclaw.json
2026-04-24 10:16:41.116932+00:00Problem:
2026-04-24 10:16:41.118801+00:00- plugins.entries.memory-core.config: invalid config: must NOT have additional properties
2026-04-24 10:16:41.120353+00:002026-04-24T10:16:41.120353959Z
2026-04-24 10:16:41.122453+
#Dreaming related config fails to load in 2026.04.22 but works in 2026.04.15
1 messages · Page 1 of 1 (latest)
Let me check the schema before I guess.
I checked the current schema, and that one is annoying.
That error means plugins.entries.memory-core.config has extra top level keys. For memory-core, the only valid top level key there is dreaming.
So this shape is valid:
plugins: {
entries: {
"memory-core": {
config: {
dreaming: {
enabled: true,
frequency: "0 3 * * *",
timezone: "UTC",
},
},
},
},
}
If you currently have things like enabled, frequency, phases, etc directly under config, move them under config.dreaming.
Please paste these two things next:
openclaw --version- just your
plugins.entries.memory-coreblock
If you already do have everything under dreaming, then 2026.04.22 is probably rejecting a specific extra dreaming key, and I can point to the exact offender once I see the snippet.
Docs:
https://docs.openclaw.ai/reference/memory-config#dreaming
No? This works in 15 but fails in 22:
"plugins": {
"entries": {
"google": {
"enabled": true
},
"openai": {
"enabled": true
},
"github-copilot": {
"enabled": true
},
"openrouter": {
"enabled": true
},
"memory-core": {
"config": {
"dreaming": {
"enabled": true
}
}
}
}
},
That snippet should be valid. Let me verify whether 2026.04.22 had a regression or if the running install is seeing the wrong plugin schema.
Yep, you’re right, that snippet is valid.
I checked the current bundled memory-core schema, and this is allowed:
plugins.entries["memory-core"].config.dreaming.enabled
So if 2026.04.15 works and 2026.04.22 fails on exactly that, I would treat it as a plugin/schema loading regression or stale bundled files, not a bad config on your side.
The clue is the error path:
plugins.entries.memory-core.config: ... must NOT have additional properties
That usually means the running build is seeing a memory-core schema that does not know about dreaming at all, which is wrong.
Please paste these next: