openclaw - 💡(How to fix) Fix Bug: sessions.json grows unbounded due to static schema serialized into dynamic session state [1 comments, 2 participants]

TL;DR

Store static configuration data in a global in-memory cache and serialize only a lightweight reference in each session entry to reduce data bloat.

Guidance

• Identify the static data (skillsSnapshot and systemPromptReport) that is being duplicated across every session entry and determine the best approach to cache or load it dynamically.
• Consider implementing Option A, which involves storing the static data in a global in-memory cache computed once on startup, and serializing only a lightweight reference in each session entry.
• Evaluate the trade-offs between Option A and Option B, which involves loading the static data on-demand and not persisting it to sessions.json.
• Verify the effectiveness of the chosen approach by measuring the reduction in session data size and improvement in performance.

Example

// Example of storing skillsSnapshot in a global in-memory cache
const skillsSnapshotCache = {};
function getSkillsSnapshot() {
  if (!skillsSnapshotCache.snapshot) {
    // Compute skillsSnapshot once on startup
    skillsSnapshotCache.snapshot = computeSkillsSnapshot();
  }
  return skillsSnapshotCache.snapshot;
}

// Serialize only a lightweight reference in each session entry
const sessionEntry = {
  // ...
  skillsSnapshotRef: 'v2026.4.11',
  // ...
};

Notes

The chosen approach may have implications for data consistency and availability, particularly if the static data is updated frequently. It is essential to consider these factors when implementing the solution.

Recommendation

Apply workaround by storing static configuration data in a global in-memory cache and serializing only a lightweight reference in each session entry, as this approach is likely to significantly reduce data bloat and improve performance.