Engram – Persistent Memory API with Drift Detection for AI Agents
Mem0 stores facts, but Engram detects when they go stale and break your agent.
A brain-inspired, portable context database for AI agents
Multi-agent-safe memory with reinforcement—beats append-only summaries but early v0.1.
AI engineers building long-running agents, multi-agent systems, LLM application developers
LangSmith · Langchain Memory · Mem0
I’ve been working on Engram, a persistent context layer for AI agents and LLM sessions.
The inspiration came from a simple problem: when you work with LLMs for a long time, context collapses. Conversation history gets too long, summaries drift, and models forget or mix up earlier decisions. It becomes even worse when multiple agents or different models are involved.
Engram is an attempt to treat AI memory more like how human memory works: * knowledge is stored incrementally * related concepts reinforce each other * context is reconstructed when needed rather than replaying the entire past
Instead of storing conversations as raw text or chunks, Engram commits information into a persistent context structure and then materializes the relevant pieces when a model needs them.
Some other capabilities built so far: * multi-agent updates to the same context * evolving knowledge instead of append-only memory * context reconstruction across long sessions * working across models (e.g. start in ChatGPT, continue in Claude)
Repo: https://github.com/softmaxdata/engram
Would love feedback from people building agents or long-running AI workflows. Happy to answer questions or run experiments people suggest.
Mem0 stores facts, but Engram detects when they go stale and break your agent.
Hippocampal memory model for Claude runs entirely in-browser, no API—genuinely novel architecture.
Three-method API for agent memory, but semantic memory systems aren't novel anymore.
Cross-provider agent memory is clever, but LLM context windows keep growing and RAG is already standard.
Navigation-over-search architecture sounds great until you realize it's just another RAG wrapper.
GraphDB for agents with schema enforcement—clever idea, but early and positioning unclear.