memory-lancedb-pro plugin repeatedly loads and may cause provider issues

[nak1li]

Plugin Version: 1.1.0-beta.9

OpenClaw Version: 2026.3.24

Environment:

• Ubuntu Linux
• Node v24.14.0

Bug Description:
memory-lancedb-pro plugin appears to be repeatedly loaded/registered in the logs during gateway startup. Each registration creates a new hook registration entry.

Expected Behavior:
Plugin should load once and register hooks only once.

Actual Behavior:
Logs show repeated plugin registration:

Mar 26 19:07:51 nakili-ubuntu node[626855]: memory-lancedb-pro@1.1.0-beta.9: plugin registered
Mar 26 19:07:51 nakili-ubuntu node[626855]: memory-lancedb-pro: loaded without install/load-path provenance

This happens multiple times in rapid succession during startup.

Additional Context:
Similar to issue #368, there may be interaction issues with other providers when memory-lancedb-pro is enabled. Disabling the plugin may resolve provider startup issues.

Questions:

1. Is repeated plugin loading expected behavior?
2. Could this cause instability with other providers (Feishu, etc.)?
3. Any recommended workarounds while waiting for fix?

[AliceLJY]

Known issue — this is the same root cause as #351 (register() called multiple times per message).

The plugin's register() lacks an idempotent guard, so it gets invoked on every gateway message cycle instead of once. Each call re-registers hooks, which can interfere with other providers.

Fixes in progress:

• PR fix: auto-captured memories write confirmed state to unblock autoRecall #354 (auto-capture pending state fix)
• PR fix: prevent autoRecall context inflation (#345) #353 (autoRecall context inflation fix)
• Issue fix: idempotent register guard + governance filter observability #366 also tracks adding an idempotent register guard

Workaround for now: if it's causing provider issues, disable the plugin until the fix lands.

[AliceLJY]

Duplicate of #351. Fix tracked in PR #365. Closing.