Skip to main content
Memory that never forgets is memory you can’t trust. Nora gives you three ways to clean things up, most of them reversible.

​
Ways to clean up

Soft-deletes an item so it stops appearing in retrieval. Where you do it differs by paradigm:
  • Wiki the ⋯ menu at the top-right of the editor → Exclude from search
  • Index (vector) Facts tab, hover a row → X button on the right
  • Index (graph) Graph tab, select nodes/edges → Delete
  • Evolution Graph tab, select a node → Delete. An Undo toast appears right after (click within a few seconds to reverse)

​
Supersede on conflict (Index only)

An automatic policy for handling new facts that conflict with existing ones. Toggle Settings → Advanced → Supersede on conflict on the Index space.
  • On the new fact wins and the old one becomes history. Old fact drops out of retrieval.
  • Off (default) both facts coexist and retrieval returns both. Reconcile later by hand.
Turn on for natural-refresh cases like “customer tier was Gold, now Platinum.”

​
Importance decay (Index only)

Index spaces use a recency-decay half-life τ (days). Facts not retrieved for a while lose score gradually and naturally slide out of results. Adjust τ under Index Settings → Advanced → retrieval tuning.
  • Default 14 days Recent facts show relatively higher.
  • A long half-life Set it long, like 180 days, and old facts hold up as well as new ones. Good for glossaries and settled procedures.
  • To turn it off effectively, set τ very high or drop the recency weight to 0
Wiki doesn’t apply this decay automatically. Unused notes don’t disappear on their own: clean them up by hand, or add a cleanup instruction to the memory agent’s policy prompt.

​
Other reasons an Agent seems to “forget”

Memory that looks missing isn’t always deleted. Also common:
  • Scope changed passing a different user_id or thread_id per run puts you in a different scope where the memory doesn’t live
  • The memory agent consolidated it several notes were merged into a summary note; the content is still there, just inside another item
  • Index decay pushed it down an old fact dropped below the top-N cutoff
To figure out “why does the Agent know less now than earlier?”, check the memory operations in the trace. Each read is logged with its query, scope, and returned items.

​
Audit

Every memory event is recorded in the space’s Log tab in chronological order (except Session: the conversation itself is the log). Use it to see when adds, edits, and deletes happened.