Memory that tidies itself after you respond.
After writes and reads, MemState can merge obvious duplicates and soften topics that have gone quiet. That work is intentionally asynchronous so your user-facing paths stay snappy.
Why background care matters
Without it, long-running agents accumulate near-duplicate notes and stale facts that pollute retrieval. With it, the corpus stays searchable without manual database janitor work after every session.
What you should expect
Policies favor non-destructive changes: consolidation and archival adjust what is easy to find, not what is permanently erased. Tune aggressiveness when you understand your traffic patterns.
Continue
- Cleaning duplicates (product view)
- Letting memory fade (product view)