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
- Configure
plugins.slots.memory = "memory-lancedb-pro" and enable the plugin.
- Start OpenClaw 2026.4.1.
- Confirm the plugin is functional with
openclaw plugins info memory-lancedb-pro and openclaw memory-pro stats.
- Run
openclaw doctor --non-interactive.
- 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(...).
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
memory-lancedb-pro is loaded and functional, but
openclaw doctor --non-interactivereportsNo active memory plugin is registered for the current config.This looks like a false positive. Local diagnosis suggests the plugin does not callapi.registerMemoryRuntime(...)while built-inmemory-coredoes.Steps to reproduce
plugins.slots.memory = "memory-lancedb-pro"and enable the plugin.openclaw plugins info memory-lancedb-proandopenclaw memory-pro stats.openclaw doctor --non-interactive.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 correspondingregisterMemoryRuntime(...)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(...).