Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix status/doctor reports memory unavailable while memory-lancedb-pro appears registered at runtime [1 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#59942•Fetched 2026-04-08 02:38:30
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
lamkan0210lamkan0210
Participants
lamkan0210lamkan0210

After upgrading to OpenClaw 2026.4.2, the runtime logs suggest memory-lancedb-pro is successfully loaded and registered, but CLI health/status commands still report memory as unavailable/inactive.

This may be a mismatch between runtime plugin registration and the logic used by openclaw status / openclaw doctor to detect an active memory plugin.

Related plugin-side issue: https://github.com/CortexReach/memory-lancedb-pro/issues/472

Error Message

Runtime/plugin logs:

Root Cause

After upgrading to OpenClaw 2026.4.2, the runtime logs suggest memory-lancedb-pro is successfully loaded and registered, but CLI health/status commands still report memory as unavailable/inactive.

This may be a mismatch between runtime plugin registration and the logic used by openclaw status / openclaw doctor to detect an active memory plugin.

Related plugin-side issue: https://github.com/CortexReach/memory-lancedb-pro/issues/472

Code Example

[plugins] memory-lancedb-pro@1.1.0-beta.10: plugin registered (db: /Users/qianglin/.openclaw/memory/lancedb-pro-1024, model: bge-large:latest, smartExtraction: ON)
[plugins] memory-lancedb-pro: smart extraction enabled (LLM model: openai/gpt-oss-120b, timeoutMs: 30000, noise bank: ON)
[plugins] session-memory: hook registered for command:new as memory-lancedb-pro-session-memory

---

Memory: enabled (plugin memory-lancedb-pro) · unavailable

---

No active memory plugin is registered for the current config.
RAW_BUFFERClick to expand / collapse

Summary

After upgrading to OpenClaw 2026.4.2, the runtime logs suggest memory-lancedb-pro is successfully loaded and registered, but CLI health/status commands still report memory as unavailable/inactive.

This may be a mismatch between runtime plugin registration and the logic used by openclaw status / openclaw doctor to detect an active memory plugin.

Related plugin-side issue: https://github.com/CortexReach/memory-lancedb-pro/issues/472

Environment

  • OpenClaw: 2026.4.2
  • OS: macOS 26.5 (arm64)
  • Node: 25.6.0
  • Memory plugin shown in logs: [email protected]

Observed behavior

Runtime/plugin logs:

[plugins] [email protected]: plugin registered (db: /Users/qianglin/.openclaw/memory/lancedb-pro-1024, model: bge-large:latest, smartExtraction: ON)
[plugins] memory-lancedb-pro: smart extraction enabled (LLM model: openai/gpt-oss-120b, timeoutMs: 30000, noise bank: ON)
[plugins] session-memory: hook registered for command:new as memory-lancedb-pro-session-memory

But openclaw status shows:

Memory: enabled (plugin memory-lancedb-pro) · unavailable

And openclaw doctor --non-interactive shows:

No active memory plugin is registered for the current config.

Expected behavior

If the memory plugin is loaded/registered and usable at runtime, status and doctor should report that consistently.

Actual behavior

Runtime logs look healthy, but status / doctor still report memory as unavailable or inactive.

Hypothesis

Possible mismatch between:

  • runtime plugin registration / hooks
  • CLI-side "active memory plugin" detection
  • health probe/status rendering path

It may be checking a different registration source/path than the one used by the running plugin.

extent analysis

TL;DR

Investigate and potentially update the logic used by openclaw status and openclaw doctor to detect an active memory plugin, ensuring consistency with runtime plugin registration.

Guidance

  • Review the related plugin-side issue https://github.com/CortexReach/memory-lancedb-pro/issues/472 for potential insights or fixes.
  • Compare the registration source/path used by the running plugin with the one checked by openclaw status and openclaw doctor to identify any discrepancies.
  • Verify that the memory-lancedb-pro plugin 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 the memory plugin is loaded/registered and usable at runtime, status and doctor should report that consistently.

#callback error#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING