Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: memory-lancedb-pro loaded and working, but doctor/status reports no active memory plugin [1 pull requests, 1 comments, 2 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#60177•Fetched 2026-04-08 02:35:26
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
Lrs-GreenBottleLrs-GreenBottle
Participants
Lrs-GreenBottleLrs-GreenBottlemartingarramonmartingarramon
Timeline (top)
labeled ×2commented ×1

memory-lancedb-pro is loaded and functional, but openclaw doctor --non-interactive reports No active memory plugin is registered for the current config. This looks like a false positive. Local diagnosis suggests the plugin does not call api.registerMemoryRuntime(...) while built-in memory-core does.

Root Cause

memory-lancedb-pro is loaded and functional, but openclaw doctor --non-interactive reports No active memory plugin is registered for the current config. This looks like a false positive. Local diagnosis suggests the plugin does not call api.registerMemoryRuntime(...) while built-in memory-core does.

Fix Action

Fix / Workaround

Workaround: verify health using openclaw plugins info memory-lancedb-pro, openclaw memory-pro stats, memory_store, and memory_recall instead of relying on doctor/status. Suspected fix: register a memory runtime for memory-lancedb-pro exposing at least getMemorySearchManager(...) and resolveMemoryBackendConfig(...).

PR fix notes

PR #65066: fix(memory-lancedb): register runtime for doctor and status

Description (problem / solution / changelog)

Summary

  • register a memory capability runtime for memory-lancedb so core doctor/status surfaces can discover it as the active memory plugin
  • expose the minimal runtime hooks doctor/status need: backend config resolution, search-manager status, embedding probe, and vector probe
  • add regression coverage proving the plugin registers a visible runtime instead of only tools/hooks

Problem

memory-lancedb is a kind: "memory" plugin, but it did not register a memory runtime/capability. That meant the core memory-runtime path had nothing to resolve, so doctor/status could incorrectly report that no active memory plugin was registered even when the plugin was installed and working.

Validation

  • pnpm vitest run extensions/memory-lancedb/index.test.ts
  • pnpm lint extensions/memory-lancedb/index.ts extensions/memory-lancedb/index.test.ts
  • pnpm build --filter memory-lancedb

Fixes #60177

Changed files

  • extensions/memory-lancedb/index.test.ts (modified, +107/-0)
  • extensions/memory-lancedb/index.ts (modified, +121/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

memory-lancedb-pro is loaded and functional, but openclaw doctor --non-interactive reports No active memory plugin is registered for the current config. This looks like a false positive. Local diagnosis suggests the plugin does not call api.registerMemoryRuntime(...) while built-in memory-core does.

Steps to reproduce

  1. Configure plugins.slots.memory = "memory-lancedb-pro" and enable the plugin.
  2. Start OpenClaw 2026.4.1.
  3. Confirm the plugin is functional with openclaw plugins info memory-lancedb-pro and openclaw memory-pro stats.
  4. Run openclaw doctor --non-interactive.
  5. Observe the warning even though memory_store / memory_recall / stats are working.

Expected behavior

doctor/status should recognize memory-lancedb-pro as the active memory backend when the plugin is loaded and operational.

Actual behavior

doctor reports No active memory plugin is registered for the current config. In the same environment, the plugin shows as loaded, memory stats are available, memory_store and memory_recall work, and mdMirror writes to markdown.

OpenClaw version

2026.4.1

Operating system

macOS arm64

Install method

No response

Model

minimax-portal/MiniMax-M2.7-highspeed

Provider / routing chain

openclaw -> memory-lancedb-pro -> LanceDB / Ollama (nomic-embed-text)

Additional provider/model setup details

Environment: OpenClaw 2026.4.1, memory-lancedb-pro 1.1.0-beta.9, macOS arm64. Active slot is plugins.slots.memory = "memory-lancedb-pro". Core checks active backend via memory runtime, but memory-lancedb-pro appears to register tools / CLI / services / hooks without a corresponding registerMemoryRuntime(...) call.

Logs, screenshots, and evidence

Impact and severity

Severity: medium. Actual memory operations work, but doctor/status show a misleading warning that makes the memory backend look unhealthy.

Additional information

Workaround: verify health using openclaw plugins info memory-lancedb-pro, openclaw memory-pro stats, memory_store, and memory_recall instead of relying on doctor/status. Suspected fix: register a memory runtime for memory-lancedb-pro exposing at least getMemorySearchManager(...) and resolveMemoryBackendConfig(...).

extent analysis

TL;DR

The most likely fix is to register a memory runtime for the memory-lancedb-pro plugin, exposing necessary methods like getMemorySearchManager and resolveMemoryBackendConfig.

Guidance

  • Verify the plugin's functionality using openclaw plugins info memory-lancedb-pro, openclaw memory-pro stats, memory_store, and memory_recall to ensure it's working as expected despite the doctor/status warning.
  • Investigate the memory-lancedb-pro plugin's code to identify why it doesn't call api.registerMemoryRuntime(...), which is likely the cause of the issue.
  • Consider implementing a workaround by ignoring the doctor/status warning and relying on the plugin's own health checks, as suggested in the issue.
  • Review the OpenClaw documentation to understand how to properly register a memory runtime for a custom plugin like memory-lancedb-pro.

Example

No specific code example can be provided without more context about the plugin's codebase, but the fix would involve adding a call to api.registerMemoryRuntime(...) in the memory-lancedb-pro plugin, passing in an object that implements the required methods (e.g., getMemorySearchManager and resolveMemoryBackendConfig).

Notes

The provided information suggests that the issue is specific to the memory-lancedb-pro plugin and its interaction with OpenClaw. Without access to the plugin's code or more detailed documentation, it's challenging to provide a precise fix. However, registering a memory runtime as described seems to be the most direct path to resolving the issue.

Recommendation

Apply a workaround by verifying the plugin's health through its own commands and ignoring the doctor/status warning until a proper fix can be implemented by registering a memory runtime for the memory-lancedb-pro plugin. This approach allows for continued use of the plugin despite the misleading warning.

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

doctor/status should recognize memory-lancedb-pro as the active memory backend when the plugin is loaded and operational.

#api#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