compact-memory

To reduce context bloat, you can compress memory rule files by archiving session entries older than 30 days and pruning obsolete decisions that reference deleted project files. This memory hygiene process keeps your workspace queryable and lean.

The best way to archive old memory sessions is to retain the 4 most recent entries in your memory rules file while moving entries older than 30 days into a designated Archive block. This preserves recent context while clearing stale session bloat.

Syncing project facts to a memory graph improves performance by extracting high-signal facts into queryable entities. This allows future sessions to retrieve essential project knowledge without loading and processing large, bloated memory rule files.

To prune dead memory decisions, audit your memory rules file and remove entries tied to tools, files, or patterns that no longer exist in the project. This ensures your context only retains decisions relevant to the current codebase.

Yes, syncing durable facts to a memory graph requires an MCP memory server. The process uses the memory MCP to create 3 to 5 queryable entities, allowing future sessions to access key project facts without reloading full memory rule files.

You should compress memory rule files when context grows over time and older sessions degrade performance or relevance. If your project accumulates stale decisions and long-term session bloat, running a memory hygiene cycle restores queryability.