Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: memory-core enabled but status reports Memory unavailable on v2026.4.25 [3 comments, 3 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#72907•Fetched 2026-04-28 06:30:28
View on GitHub
Comments
3
Participants
3
Timeline
5
Reactions
0
Author
RamaAditya49RamaAditya49
Participants
RamaAditya49RamaAditya49shrimpy8shrimpy8steipetesteipete
Timeline (top)
commented ×3closed ×1subscribed ×1

After upgrading a Linux VPS from OpenClaw 2026.4.24 to 2026.4.25, openclaw status reports:

Memory enabled (plugin memory-core) · unavailable

The gateway itself is reachable and Telegram works, but the memory status appears unavailable in the post-upgrade status report.

Error Message

If memory-core is enabled, status should either show its ready/error state with actionable detail, or provide a diagnostic reason for why memory status is unavailable.

Root Cause

This creates uncertainty during upgrade verification because the gateway and channel can be healthy while memory appears degraded.

Code Example

Memory enabled (plugin memory-core) · unavailable

---

Gateway ... reachable ... app 2026.4.25
Gateway service systemd installed · enabled · running
Memory enabled (plugin memory-core) · unavailable
Plugin compatibility none
Tasks 0 active · 0 queued · 0 running · 3 issues · audit clean · 35 tracked

---

"memory": null,
"memoryPlugin": {
  "enabled": true,
  "slot": "memory-core"
}
RAW_BUFFERClick to expand / collapse

Summary

After upgrading a Linux VPS from OpenClaw 2026.4.24 to 2026.4.25, openclaw status reports:

Memory enabled (plugin memory-core) · unavailable

The gateway itself is reachable and Telegram works, but the memory status appears unavailable in the post-upgrade status report.

Environment

  • OpenClaw: 2026.4.25 (aa36ee6)
  • OS: Linux 6.6.117-45.2.oc9.x86_64 x64
  • Node: 24.14.0
  • Gateway: systemd, loopback bind 127.0.0.1:18789
  • Memory plugin: memory-core

Evidence

openclaw status --deep --timeout 10000 reports:

Gateway ... reachable ... app 2026.4.25
Gateway service systemd installed · enabled · running
Memory enabled (plugin memory-core) · unavailable
Plugin compatibility none
Tasks 0 active · 0 queued · 0 running · 3 issues · audit clean · 35 tracked

openclaw status --json --deep contains:

"memory": null,
"memoryPlugin": {
  "enabled": true,
  "slot": "memory-core"
}

Expected behavior

If memory-core is enabled, status should either show its ready/error state with actionable detail, or provide a diagnostic reason for why memory status is unavailable.

Actual behavior

The status output only says memory is unavailable, without enough detail to determine whether this is a real memory subsystem failure or a status/reporting regression.

Impact

This creates uncertainty during upgrade verification because the gateway and channel can be healthy while memory appears degraded.

extent analysis

TL;DR

The issue with the memory status appearing as unavailable after upgrading OpenClaw to version 2026.4.25 may be resolved by investigating plugin compatibility and configuration.

Guidance

  • Verify the compatibility of the memory-core plugin with OpenClaw version 2026.4.25 to ensure it is supported.
  • Check the configuration of the memory-core plugin to ensure it is correctly set up and enabled.
  • Run openclaw status --deep --timeout 10000 and openclaw status --json --deep to gather more detailed information about the memory status and plugin configuration.
  • Investigate the systemd service logs for any errors related to the memory-core plugin.

Example

No code snippet is provided as the issue does not require a code change, but rather an investigation into the plugin configuration and compatibility.

Notes

The issue may be specific to the 2026.4.25 version of OpenClaw, and further investigation is needed to determine the root cause. The memory-core plugin may require additional configuration or updates to work correctly with the new version.

Recommendation

Apply workaround: Investigate and resolve any plugin compatibility issues, and verify the configuration of the memory-core plugin to ensure it is correctly set up and enabled. This is recommended as the issue appears to be related to the plugin configuration and compatibility rather than a bug in the OpenClaw version.

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…

FAQ

Expected behavior

If memory-core is enabled, status should either show its ready/error state with actionable detail, or provide a diagnostic reason for why memory status is unavailable.

#model download#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: memory-core enabled but status reports Memory unavailable on v2026.4.25 [3 comments, 3 participants]