Bug type

Behavior bug (incorrect output/state without crash)

Summary

On OpenClaw 2026.5.2 (Windows, npm global install), lossless-claw appears loaded (status=loaded, enabled=true) but the context engine is not registered, causing fallback to legacy. The warning [context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy" persists after uninstall/reinstall and config verification.

Steps to reproduce

1. Run openclaw plugins update --all to install lossless-claw 0.9.3.
2. Observe duplicate plugin id warning: a global plugin overwrites another global plugin at ~/.openclaw/extensions/lossless-claw.
3. Run openclaw plugins list --json and confirm lossless-claw shows status: loaded and enabled: true.
4. Confirm plugins.slots.contextEngine = "lossless-claw" in openclaw.json.
5. Start or restart the gateway.
6. Observe in gateway logs:

   [context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".
   

7. Note: Uninstalling and reinstalling lossless-claw via openclaw plugins uninstall / openclaw plugins install does not resolve the issue.

Expected behavior

When plugins.slots.contextEngine = "lossless-claw" and plugins.entries.lossless-claw.enabled = true, the lossless-claw context engine should be registered and active at runtime, with no fallback to legacy.

Actual behavior

The lossless-claw plugin loads successfully but the context engine is not registered. Gateway falls back to legacy engine. The LCM database (lcm.db) is present (224MB, contains data) but is not being used because the context engine is not active.

Environment details

• OpenClaw version: 2026.5.2
• OS: Windows 10.0.26200 (x64)
• Install method: npm global at C:\Users\zhang\AppData\Roaming\npm\node_modules\openclaw
• Node.js: 24.15.0
• lossless-claw version: 0.9.3 (installed at C:\Users\zhang\.openclaw\npm\node_modules\@martian-engineering\lossless-claw)
• Secondary lossless-claw copy at: C:\Users\zhang\AppData\Roaming\npm\node_modules\@martian-engineering\lossless-claw (installed as OpenClaw dependency)
• Old extension directory renamed to: C:\Users\zhang\.openclaw\extensions\_disabled_lossless-claw
• lcm.db exists at C:\Users\zhang\.openclaw\lcm.db (224MB, last modified 2026-05-04 08:48:15)
• Gateway log location: C:\tmp\openclaw\openclaw-2026-05-04.log

Additional observation: duplicate plugin id warning

Before the context-engine issue, the following warning appears at startup:

[plugins] Duplicate plugin id "lossless-claw" — a global plugin is overwriting another global plugin.
Source: C:\Users\zhang\.openclaw\extensions\lossless-claw

This suggests the old extension directory (~/.openclaw/extensions/lossless-claw) was not fully cleaned before the new installation path was registered, causing a conflict.

Impact

The lossless-claw context engine is inactive. All sessions use the legacy engine instead. The LCM memory system积累的数据无法被使用.

Related issues

• [Bug]: lossless-claw selected and enabled but not registered as context engine in 2026.5.2 #77063: Same symptom (lossless-claw not registered as context engine in 2026.5.2) — closed as "already implemented in main"
• This issue persists on 2026.5.2 because the fix is in main but not yet released in a stable version.

Logs

[context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".
[plugins] memory-lancedb-pro: plugin registered (db: C:\Users\zhang\.openclaw\memory\lancedb-pro, model: Qwen/Qwen3-Embedding-8B, smartExtraction: ON)
[plugins] Duplicate plugin id "lossless-claw" — a global plugin is overwriting another global plugin.
Source: C:\Users\zhang\.openclaw\extensions\lossless-claw