#memory-core: narrative session cleanup fail

1 messages · Page 1 of 1 (latest)

stark kindle
#

@hidden scroll Seeing a recurring non-fatal error after every memory-core dream phase:

memory-core: narrative session cleanup failed for light phase: missing scope: operator.admin

Fires after both light and REM phases on every gateway boot, across all workspaces. Gateway is on 2026.4.15. Dreaming is enabled, diary entries write successfully — the error only appears on the cleanup step that follows.

Is operator.admin a scope that needs to be explicitly granted somewhere in openclaw.json, or is this a known bug in memory-core? Any workaround short of disabling dreaming entirely?

hidden scrollBOT
#

Let me check the docs and source so I don’t guess.

#

I found the exact cleanup path in memory-core, now I’m checking whether it’s a config requirement or just a scope mismatch bug.

#

This looks like a bug, not a missing openclaw.json scope.

I checked the current source, and the cleanup path is:

  • memory-core writes the dream diary entry
  • then calls subagent.deleteSession(...)
  • that dispatches sessions.delete
  • sessions.delete requires operator.admin
  • the internal synthetic plugin client defaults to operator.write

So the phase succeeds, then cleanup warns with missing scope: operator.admin.

Short version:

  • No, this is not a scope you should add under plugins.entries.memory-core.config.
  • I do not see a supported config knob to disable only this cleanup/diary subagent path.
  • If diary entries are writing fine, this is basically a non-fatal cleanup bug / log-noise bug.