Memory Tiers

• Risk level: Low
• Analyzed: Feb 21, 2026, 5:52 AM
• Findings: 0
• Version: 0.1.0

Overview

The skill's code and instructions are consistent with a local tiered-memory manager: it scans agent session transcripts, tracks accesses, and moves sections between workspace files — no network exfiltration or unrelated credentials are requested.

This skill is coherent with its purpose but behaves on local data: it scans your agent session transcripts (~/.openclaw/agents/...), and writes access metadata and moved content into workspace files and state/*.json. Before installing or running: (1) Inspect state/ and workspace backups — the scripts will edit MEMORY.md and other memory files when not in --dry-run. (2) Be aware session transcripts can contain sensitive user data; tracked snippets and queries are stored in state/access-log.json and searches[]. If that is a concern, run track.js with a restricted --sessions-dir or smaller --since window, review the log file format, or sanitize transcripts first. (3) Use --dry-run for maintain.js to preview changes. (4) Confirm file permissions on the workspace and state directories if you want the logs to be inaccessible to other users. (5) If you want additional assurance, review/modify the scripts (they are short and local) to redact or avoid storing raw content.