openclaw - 💡(How to fix) Fix Session conversation history not restored after OpenClaw update (LCM "Not found") [1 participants]

Problem

After updating OpenClaw (from 2026.3.28 to 2026.4.2), the PM agent's session lost access to all previous conversation history stored in LCM (lossless-claw).

Symptoms:

• The session key appears identical before and after the update: agent:pm:direct:4f45369c7db6c212b715743c37104fbb
• lcm_describe(sessionKey) returns "Not found" for the current session
• However, LCM grep confirms older messages (msg#5381-5395, timestamps 16:13-16:23 GMT+8 on 2026-04-03) exist in the database and are linked to summaries (sum_0b896d5f10434f7c, sum_ac01217d3b092a04)
• The agent cannot access afternoon's conversations from the same session key

Expected behavior:

• Session history should be preserved and accessible after gateway restart/update, as documented

Actual behavior:

• LCM "loses" the association between the current session key and previously stored conversation history
• The session key looks identical, but LCM treats it as a new/unknown session

Environment

• OpenClaw: 2026.4.2 (previously 2026.3.28)
• lossless-claw: 0.5.2
• Node.js: 24.13.0
• OS: Windows_NT
• Channel: qqbot

Steps to Reproduce

1. Have an active PM agent session with LCM-compacted conversation history
2. Update OpenClaw (gateway restart after update)
3. Agent loses access to all pre-update conversation history

Questions / Debugging Info

• Could this be related to session ID format changes between versions?
• Is there a migration step for LCM's SQLite database that should have run but didn't?
• Is the session key in LCM derived differently after the update?

Additional Context

The LCM database (~/.openclaw/lcm.db) still contains the old conversation records - they are not deleted. The issue appears to be at the session-to-conversation mapping level, not data loss.