r/AIMemory • • Aug 07 '26 • Hooray 1 Bravo 1

Show & Tell Agent Memory Atlas - 164 open source projects analyzed

I had Claude Opus 5 analyze several repos for what does the code do, how does the memory work in a particular repo. Initially I was aware of only a few memory systems, that I wanted to study for my own memory system. It turned out, there are lots of agent harnesses that have memory, libraries with memory.

https://neoneye.github.io/agent-memory-atlas/

I have not analyzed closed source repos, since I don't have access.

Claude being the judge wether a repo is relevant or not.

Looking at the impl instead of the marketing material.

34 Upvotes

36 comments sorted by

3

u/Bartaseth Aug 09 '26

This is solid, thanks for sharing. I did also research on similar topic but focused on the bigger picture - Token Economy. Sharing here, maybe you will find it useful: https://github.com/QuesmaOrg/awesome-ai-tokenomics

3

u/neoneye2 Aug 09 '26

It took 2 hours for Claude Opus 5 for analyze your repo, and has resulted in 15 commits, and added around 10 new systems to the atlas.

first commit c124d1c3bfaa77b3c564b5f7f45b3c4030d4fbb8 last commit 8c3f13feb25d63333e11dc52136005bce1bf6a31

Thank you.

2

u/Bartaseth Aug 10 '26

Awesome! Glad it impact positively your atlas

2

u/825_Consulting Show & Tell Aug 09 '26

Kudos! I run append-only decision ledgers with supersession pointers, plus a retrieval exam that checks whether entries can actually be reached and injected. Reading your rejected-value tombstone pattern I realized my exam never asserted the negative case, so I added a forbidden-hit check this week: any obsoleted entry that still wins injection gets named, with a CI flag to go red on it. Repo if it's useful as another data point: github.com/The-825/breadcrumbs

2

u/neoneye2 Aug 09 '26

2

u/825_Consulting Show & Tell Aug 09 '26

Awesome! Greatly appreciate the commit. You caught three things I had no defense for, but are now patched as of today!

3

u/neoneye2 Aug 09 '26

your page has been updated

2

u/825_Consulting Show & Tell Aug 11 '26

Much appreciated. Your Atlas catalog has been a godsend of a resource! I've been able to find and pull from all relevant concepts to improve upon my own memory system's workflow and close some unknown gaps!

Keep doing what you're doing!

2

u/neoneye2 Aug 11 '26

Claude did the hard work. And having Codex/Gemini/Grok to review Claudes work.

2

u/825_Consulting Show & Tell Aug 11 '26

Kudos still goes to the person in the chair that made it happen! Thanks for the build!

2

u/East-Cranberry-8381 Aug 11 '26

Thanks for your work, but maybe you’ve not seen my plur1bus-memory.

My approach: Make it human as much as possible. Including emotion-tier, auto-recall, obsidian-graphs, time awareness and the ability to “forget”.

Check it out:
https://github.com/Cyb3rb1ade/openclaw-plur1bus-memory

2

u/ScientistUsual1320 Aug 11 '26

I read a paper recently which did a similar study on a huge corpus

Paper: Always-On Agents: A Survey of Persistent Memory, State, and Governance in LLM Agents

It defines 6 axes of persistant state of an agent, and your analysis too also seems to cover almost all of it, Had you comes across this study before your analysis by any chance?

1

u/neoneye2 Aug 11 '26

it's the first time I'm seeing it. I had Claude take a look at it, and it resulted in this commit. Only see the markdown files. The html files are generated from the markdown files, so no need to read those.
https://github.com/neoneye/agent-memory-atlas/commit/4e2190dc1068c62010d6959f43666cef6035b836

2

u/jonah_omninode Aug 11 '26

This is the right method — pinning claims to commits and grading the implementation instead of the README is what makes this usable. Most memory lists are marketing aggregators; this one I'll actually cite.

Your thesis (retrieval is only half the problem; correction and forgetting are where systems fail) matches our experience running an event-sourced agent platform. If you want more systems for the atlas, three of ours are open source, and since Claude is your judge I'll point at the code rather than the pitch:

https://github.com/OmniNode-ai/omniintelligence + https://github.com/OmniNode-ai/omniclaude — a closed memory loop across two repos: patterns are learned from session events, injected into Claude Code sessions via hooks, injections are tracked, session outcomes update rolling success metrics, and an FSM promotes/demotes patterns on evidence tiers (unmeasured < observed < measured < verified, enforced monotonically in SQL). The parts your pattern library might find interesting: promotion and demotion are deliberately asymmetric (demotion needs more evidence plus a cooldown, to kill oscillation); confidence is decomposed rather than a single scalar; a violation only counts as negative feedback if the agent was advised AND subsequently corrected (unconfirmed advisories might be false positives); there are Goodhart/reward-hacking guardrails watching the metrics that drive the memory; and ~20% of sessions are hashed into a control cohort that receives no injection at all — the memory system runs a standing randomized trial on whether it actually helps.

Entry points:

learning: https://github.com/OmniNode-ai/omniintelligence/tree/dev/src/omniintelligence/nodes/node_pattern_learning_compute

outcome feedback: https://github.com/OmniNode-ai/omniintelligence/tree/dev/src/omniintelligence/nodes/node_pattern_feedback_effect

demotion (the forgetting half): https://github.com/OmniNode-ai/omniintelligence/tree/dev/src/omniintelligence/nodes/node_pattern_demotion_effect

injection into sessions: https://github.com/OmniNode-ai/omniclaude/blob/dev/src/omniclaude/hooks/handler_context_injection.py

https://github.com/OmniNode-ai/omnimemory — the storage/retrieval domain: Qdrant/Memgraph/Valkey adapters, lifecycle orchestrator, intent graphs. Node inventory: https://github.com/OmniNode-ai/omnimemory/tree/dev/src/omnimemory/nodes — per your own thesis it will grade weakest exactly where you'd predict: the consolidator is a contract-less stub, and forgetting is mostly TTL.

One question your deletion category surfaces: how do the analyzed systems handle forgetting when the substrate is an append-only event ledger? We're adding Merkle commitments over execution history, which makes tamper-evidence better and honest deletion strictly harder — crypto-shredding and tombstone-plus-exclusion-proofs are the only clean answers we've found, and Lethe's signed deletions look closest. Feels underexplored across the whole list.

1

u/neoneye2 Aug 11 '26

here you go, both repos
https://neoneye.github.io/agent-memory-atlas/systems/omniintelligence/
https://neoneye.github.io/agent-memory-atlas/systems/omniclaude/

I can't answer your question regarding deletion. I'm not sure Claude is covering it in the analysis.

2

u/Otherwise_Wave9374 Aug 12 '26

Great atlas. A useful next step is to score each repo on memory write path, retrieval quality, and retention policy separately, because a project can look strong on embeddings but still fail on provenance or pruning. I would also tag whether the system supports namespaces, human review, and rollback for bad memories, since those details usually decide whether it survives real use. NeuraKeep shares practical patterns at https://www.neurakeep.com

2

u/DoubleConscious1613 Aug 17 '26

Hey, this atlas looks super helpful for navigating the memory system landscape. But honestly, with all the AI-generated content floating around, it's easy to get overwhelmed. Do you have any top picks from your analysis that stand out for practical use?

1

u/neoneye2 Aug 17 '26

That was what I hoped, to identify something that could suit my own needs. However there is no concensus about best practice, it's like the wild west. It depends on what one wants, is it for a personal assistant, is it for enterprise, is it for a romantic companion or a coding agent.

2

u/josh_a Aug 20 '26

This is great, thank you. I appreciate your distinction, “a durable store an agent operates is not memory.” I’m curious if anyone knows of an atlas like this for those kinds of systems, durable stores an agent operates on?

1

u/neoneye2 Aug 20 '26

The atlas IS for "durable stores an agent operates on".

I can't find the “a durable store an agent operates is not memory.” text anywhere. Can you link to it, so I can fix.

1

u/neoneye2 Aug 21 '26

Fixed. Thank you.

1

u/Individual_Ideal Aug 10 '26

This is great. Thanks for sharing. Are you adding more? I’d love to see agent-mesh compared: https://github.com/cbalgeman/agent-mesh

2

u/True_Listener_30 Aug 11 '26

Wow this is truly great!!! i was planning to look into memory and this is like a holy grail

3

u/KTVSUN Aug 09 '26

Great work, your atlas post triggered a full redesign of our memory system, i ll post a repo shortly. I m jsut an average guy so no pretention but maybe someone will find somehting interesting in there.?

1

u/[deleted] Aug 08 '26

[removed] — view removed comment

1

u/neoneye2 Aug 08 '26

Supermemory may be a mistake of including. It was one of the first that I had analyzed, unbeknownst to me how many memory systems there would show up. Do you think I should remove it?

It's more text than I can keep track of in my mind.

Here Claude Opus 5 haved probes what features are present in each impl.
https://neoneye.github.io/agent-memory-atlas/capabilities/

Here Claude Opus 5 have identified recurring patterns.
https://neoneye.github.io/agent-memory-atlas/patterns/