Skip to content

How hippo decides what your agent remembers

Every memory has a strength. It fades on a half-life, grows each time the memory is recalled, and drops when you mark it wrong. The hippocampus inspired the design, and we tested each part on its own. On synthetic tests, outcome marks and recall strengthening helped and decay made no measurable difference. Sleep lowered recall on one scorer, and the rest is unmeasured.

  1. Buffer

    New information lands here for the session.

  2. Episodic

    Timestamped memories that fade unless they are used.

  3. Semantic

    Patterns merged from related episodes during sleep.

Marking a recall good or bad

hippo outcome --good or --bad marks the memories from the last recall. After 5 good marks and no bad ones, a memory's half-life is about 42% longer. After 3 bad marks and no good ones it decays 1.6 times as fast. On a synthetic test where every mark was correct, a bad mark cut how often a wrong memory stayed in the top five from 71.9% to 0.0%. Real marks are noisier, because --bad marks the whole recall batch.

Recall makes a memory last longer

Each recall adds 2 days to a memory's half-life, so 365 days becomes 367 and then 369. Recall ranks memories by relevance, strength and recency, and the strongest matches fill the token budget first. In the first round of our audit this helped on the synthetic test, in its best case.

Errors last twice as long

A memory stored with --error, or captured from a failed tool call, gets a 730-day half-life against the usual 365. We haven't measured whether that helps.

Decay, on a 365-day half-life

A memory's strength halves each time a half-life passes without use. The default used to be 7 days, which turned out to be a bug. On a test we registered first, the current version of a fact was in the top five 29.2% of the time at 7 days and 74.7% at 365. We did not tune 365. It tied with 730 days and with decay switched off, so on that test decay made no measurable difference. Set defaultHalfLifeDays in .hippo/config.json to choose your own, or pin a memory so it never decays.

Replacing a fact, and spotting contradictions

hippo supersede <id> "<new fact>" stores the new version and links the old one to it. The old one leaves recall and stays on record, and hippo recall --as-of <date> shows what was current on a given day. hippo reject <id> --reason "<why>" stops a value coming back at all. When two memories overlap in content and contradict each other, hippo records a conflict that hippo conflicts lists. Each memory also carries a confidence level of verified, observed, inferred or stale. None of this is measured yet.

Questions about how it works

All 14 questions

Is this just RAG?

Partly. Recall is search, BM25 plus embeddings if you install them. The difference is that the store changes as your agent works. A memory you mark wrong drops down the results, a newer fact replaces an old one, and unused memories fade.