dreaming: must NOT have additional properties | Friends of the Crustacean 🦞🤝 | Page 1

red tinsel Apr 18, 2026, 3:41 AM

#

10:35:40 [plugins] memory-core invalid config: dreaming: must NOT have additional properties
10:35:40 [plugins] 1 plugin(s) failed to initialize (validation: memory-core). Run 'openclaw plugins list' for details.

This is my setting:

      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "execution": {
              "defaults": {
                "model": "github-copilot/gpt-5-mini"
              }
            }
          }
        }
      },

tawdry arrowBOT Apr 18, 2026, 3:41 AM

#

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

untold auroraBOT Apr 18, 2026, 3:41 AM

#

pliant dirgeBOT Apr 18, 2026, 3:43 AM

#

execution is the problem.

I checked the current memory-core schema, and plugins.entries.memory-core.config.dreaming does not accept an execution block, so this fails validation with must NOT have additional properties.

Use:

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

Optional supported keys there are things like frequency, timezone, verboseLogging, storage, and phases, but not execution.

#

So for now, remove this part:

"execution": {
  "defaults": {
    "model": "github-copilot/gpt-5-mini"
  }
}

Docs:

Also, can you paste openclaw --version? I want to check whether you're on a version where this is just unsupported, or whether you've hit a schema/runtime mismatch bug.

red tinsel Apr 18, 2026, 3:47 AM

#

So how to add model into Dreaming?

pliant dirgeBOT Apr 18, 2026, 3:48 AM

#

Short answer: you can’t set a separate model for Dreaming in stock memory-core right now.

dreaming.execution.defaults.model exists in runtime code, but the public memory-core plugin schema does not expose it, so config validation rejects it.

So today, with memory-core, Dreaming is basically:

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

Supported knobs are the usual ones like frequency, timezone, verboseLogging, storage, and phases, but not execution.model.

#

Docs:

If you want per-Dreaming model override, that looks like a not-yet-exposed feature / schema mismatch, so that’s probably GitHub-issue territory: https://github.com/openclaw/openclaw/issues

Also please paste openclaw --version, because if you’re on an older build I want to rule out version skew first.

red tinsel Apr 18, 2026, 4:27 AM

#

so which does model dreaming use?

OpenClaw 2026.4.15 (041266a)

pliant dirgeBOT Apr 18, 2026, 4:28 AM

#

On 2026.4.15, Dreaming does not have its own public per-plugin model setting.

What it uses is:

Dream Diary / narrative text: a background subagent
That subagent uses the default runtime model
By default, that means it inherits the caller/main agent model
If you set a subagent default, it will use that instead:
- agents.defaults.subagents.model
- or per-agent agents.list[].subagents.model

So if you want to steer Dreaming today, the supported knob is:

{
  "agents": {

#

    "defaults": {
      "subagents": {
        "model": "github-copilot/gpt-5-mini"
      }
    }
  }
}

Important nuance: that affects subagents generally, not just Dreaming. A Dreaming-only model override is not exposed yet in memory-core, which is why dreaming.execution.defaults.model gets rejected.

Docs:

#dreaming: must NOT have additional properties