Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix memory-core: dreaming narrative generation fails with 'must have required property idempotencyKey' in 2026.4.8 [3 pull requests, 4 comments, 4 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#63214•Fetched 2026-04-09 07:56:52
View on GitHub
Comments
4
Participants
4
Timeline
8
Reactions
1
Author
kenbradbury-altkenbradbury-alt
Participants
EronFanEronFankenbradbury-altkenbradbury-altmjamivmjamivtaobingqingtaobingqing
Timeline (top)
commented ×4cross-referenced ×3referenced ×1

After upgrading to 2026.4.8, the memory-core dreaming feature logs errors during both the light and REM phase narrative generation steps. The error occurs across all configured workspaces.

Error Message

[plugins] memory-core: narrative generation failed for light phase: invalid agent params: must have required property 'idempotencyKey'
[plugins] memory-core: REM dreaming wrote reflections from 244 recent memory trace(s) [workspace=...]
[plugins] memory-core: narrative generation failed for rem phase: invalid agent params: must have required property 'idempotencyKey'

This repeats for every configured workspace (main, lite, julius in my case).

Root Cause

After upgrading to 2026.4.8, the memory-core dreaming feature logs errors during both the light and REM phase narrative generation steps. The error occurs across all configured workspaces.

Fix Action

Workaround

None currently — disabling dreaming would also disable the working candidate staging and reflection steps.

PR fix notes

PR #63245: fix(memory-core): add missing idempotencyKey to dreaming narrative subagent call

Description (problem / solution / changelog)

Fixes regression in 2026.4.8 where dreaming narrative generation fails with 'must have required property idempotencyKey'.

Issue: #63214

Changed files

  • extensions/memory-core/src/dreaming-narrative.ts (modified, +2/-0)

PR #63252: fix(memory-core): auto-generate idempotencyKey in gateway subagent runtime

Description (problem / solution / changelog)

Fix #63214

Bug: dreaming narrative generation fails with must have required property idempotencyKey in 2026.4.8

Root cause: AgentParamsSchema made idempotencyKey a required field (2026.4.8 regression), but createGatewaySubagentRuntime().run() in server-plugins.ts only passed it when explicitly provided. Dreaming code paths call subagent.run() without idempotencyKey, triggering JSON schema validation failure.

Fix: auto-generate idempotencyKey via randomUUID() when not provided, so all plugin subagent call sites continue working without modification.

Files changed: src/gateway/server-plugins.ts (1 line)

Changed files

  • src/gateway/server-plugins.ts (modified, +1/-1)

PR #63391: fix(memory-core): add missing idempotencyKey to dreaming narrative subagent call

Description (problem / solution / changelog)

Bug

memory-core dreaming narrative generation fails with 'must have required property idempotencyKey' in 2026.4.8

Root Cause

The subagent.run() call in dreaming-narrative.ts generateAndAppendDreamNarrative was missing the idempotencyKey parameter which is now required in `AgentParamsSchema'. This caused both light and REM phase narrative generation to fail on every dreaming run.

Fix

Add idempotencyKey: sessionKey to the subagent.run() call (2 lines changed).

Testing

Manual verification: patched the built dist/dreaming-looUjKfS.js on a live 2026.4.8 gateway, restarted, and confirmed narrative generation now executes (98ms vs 1ms before the fix). No more idempotencyKey errors in logs.

Original issue: GitHub #63214 Original PR (closed without merge): #63245

Changed files

  • extensions/memory-core/src/dreaming-narrative.ts (modified, +2/-0)

Code Example

[plugins] memory-core: narrative generation failed for light phase: invalid agent params: must have required property 'idempotencyKey'
[plugins] memory-core: REM dreaming wrote reflections from 244 recent memory trace(s) [workspace=...]
[plugins] memory-core: narrative generation failed for rem phase: invalid agent params: must have required property 'idempotencyKey'

---

"plugins": {
  "entries": {
    "memory-core": {
      "config": {
        "dreaming": {
          "enabled": true
        }
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Bug Report

Version: 2026.4.8 OS: Windows 10 (x64) Node: v24.14.1

Description

After upgrading to 2026.4.8, the memory-core dreaming feature logs errors during both the light and REM phase narrative generation steps. The error occurs across all configured workspaces.

Logs

[plugins] memory-core: narrative generation failed for light phase: invalid agent params: must have required property 'idempotencyKey'
[plugins] memory-core: REM dreaming wrote reflections from 244 recent memory trace(s) [workspace=...]
[plugins] memory-core: narrative generation failed for rem phase: invalid agent params: must have required property 'idempotencyKey'

This repeats for every configured workspace (main, lite, julius in my case).

Behavior

  • Dreaming still runs: candidates are staged, reflections are written
  • Only the narrative generation step fails
  • The error message suggests the agent call is missing a required idempotencyKey parameter — looks like a new required field in the agent params schema that the dreaming code isn't passing
  • Fires at the scheduled dreaming time (7:00 AM in my setup), every run

Config

Dreaming enabled via:

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

Expected Behavior

Narrative generation should complete without errors, as it presumably did in prior versions.

Workaround

None currently — disabling dreaming would also disable the working candidate staging and reflection steps.

extent analysis

TL;DR

Update the memory-core plugin configuration to include the required idempotencyKey parameter in the agent params for narrative generation.

Guidance

  • Review the memory-core plugin documentation to determine the correct format and value for the idempotencyKey parameter.
  • Verify that the idempotencyKey parameter is correctly passed to the agent during the narrative generation step by checking the plugin's code or logs.
  • Consider temporarily disabling the narrative generation step or the entire dreaming feature to prevent errors, while still allowing candidate staging and reflection steps to run.
  • Check for any updates to the memory-core plugin that may address the issue, as the problem seems to be related to a change in the required parameters.

Example

No explicit code example can be provided without more information on the memory-core plugin's API, but the fix likely involves updating the plugin's configuration to include the idempotencyKey parameter, similar to:

"plugins": {
  "entries": {
    "memory-core": {
      "config": {
        "dreaming": {
          "enabled": true,
          "agentParams": {
            "idempotencyKey": "some_unique_value"
          }
        }
      }
    }
  }
}

Notes

The exact solution depends on the specific requirements of the idempotencyKey parameter, which are not provided in the issue. Additionally, the issue may be resolved by updating to a newer version of the memory-core plugin, if available.

Recommendation

Apply workaround by updating the memory-core plugin configuration to include the required idempotencyKey parameter, as this is the most direct way to address the issue based on the provided information.

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…
#configuration error#environment variable#network issue#logging issue#authentication issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING