[Bug] openclaw status shows Memory as unavailable but plugin works correctly

[zhiangg]

Bug Description

openclaw status shows Memory as unavailable but all memory functions work correctly:

• openclaw memory-pro list works
• openclaw memory-pro search works
• memory_recall tool works
• Database read/write is fully functional

Environment

• OpenClaw version: 2026.3.28 (f9b1079)
• memory-lancedb-pro version: 1.1.0-beta.9
• OS: macOS Darwin 25.3.0

Steps to Reproduce

1. Install memory-lancedb-pro plugin
2. Run openclaw gateway restart
3. Run openclaw status → Memory shows unavailable
4. Run openclaw memory-pro list → works fine
5. Run openclaw memory-pro search test → works fine

Root Cause

The status probe checks vector.available === false to show "unavailable", but the plugin reports vector { enabled: true, available: true } in its actual state. This appears to be a timing issue where the status probe reports state before plugin fully initializes.

Expected Behavior

openclaw status should show Memory as ready when LanceDB connection is functional.

Workaround

None needed - memory functions work fine, only the status display is misleading.

[mbwmbw1337]

I am seeing the same issue as well...

[AliceLJY]

Thanks for the detailed writeup and root cause analysis! You're right — this is a timing issue in the status probe. The vector.available check can race against plugin initialization and report stale state on slower machines.

In the meantime, openclaw memory-pro stats is the reliable health check. Tracking a fix for the status probe to wait for plugin ready signal before reporting. Appreciate the clear reproduction steps!

[ldhhp]

我也是同样的问题，不过可以正常工作

[AliceLJY]

这条和 #472 / #421 属于同一类问题：插件实际可用，但 openclaw status / doctor 的状态探测会把 memory 错判成 unavailable。

对应修复已经随 PR #471 合并进主线，所以我先把这条关闭。若你在包含 #471 的最新代码/版本上还能稳定复现，再贴新日志 reopen 即可。