ENGRAM grows in the open, one release at a time — each a real step in giving an AI agent a memory it can trust, correct, and carry across sessions. Here's the story so far; the exhaustive changelog lives on GitHub Releases.
v0.5.12026-09-19
the health release
An agent that keeps a memory for months needs a way to ask whether that memory is still in good shape: how much of what it believes rests on something it has since taken back, how many of its notes it could actually find again, how many conclusions are waiting for a second look. v0.5.1 rebuilds the health score around that question. The raw counts, the signals computed from them, and the curves that turn each signal into a grade are now all written down as data rather than buried in code, so changing how strictly something is graded is a visible, versioned edit, and a build can refuse to score a graph it does not match instead of quietly producing a number. A small workbench ships with it for seeing what a change to a curve would do before making it. Two quieter additions: a memory can now point up to the more general idea it is an example of, and that chain is shown when the memory comes back, so a lesson arrives with the principle behind it; and what every hook we ship injects into the agent's context is now held under a fixed budget with the important part first, so nothing useful is lost off the end. An honest note on the grading: the curve shapes we ship are a first judgement, made by one team looking at its own graphs. They tell you where a graph stands relative to ours, not what a healthy memory looks like in general, and we expect to move them. This release also went through five release candidates in six days. Every one of them turned up something once real agents slept and woke on it, and the last thing found was a single sentence in an advisory that said the wrong thing at the right moment. We are shipping the candidate that soaked, and the fix for that sentence waits for the next release.
v0.5.02026-09-02
the cascade release
When an agent discovers that something it believed is wrong, the belief is rarely alone — other conclusions were built on top of it. v0.5.0 is about what happens next. Retracting or superseding a memory now marks every conclusion downstream of it as needing a second look, and adds a verb for working through that list and deciding, case by case, which ones still stand. Alongside it, memories now carry a short summary written at the moment they are saved, so what surfaces later is a line the agent composed while it still had the context, rather than a fragment cut out of the original afterwards. An honest note about how much the first of those has been exercised: in nearly three days of running it ourselves, we saw exactly one live marker. That is not a gap, it is the shape of the thing — a marker appears only when someone actually retracts or supersedes a belief that others were resting on, so a quiet table is what an ordinary week looks like. We are shipping it because it is correct as far as anything has shown, not because it has been through a storm.
v0.4.02026-08-20
the upkeep release
Every release so far has had a story — v0.3.2 had the evening our agents went unreachable for six hours. This one doesn't, and that is worth saying plainly: it is 107 commits of upkeep over two weeks, and most of the work went into making things that already existed survive conditions they had never been tested against. Two changes alter how the system behaves rather than what it can do. The nightly self-maintenance pass used to run all nine of its scans every night; it now draws one by weighted lottery, because running everything nightly cost far more than it found — and the measurements that proved it are in the release notes rather than assumed. And a cluster of fixes went into what an agent carries across a context reset: the moment it forgets the conversation and has to pick the thread back up from its own notes. Neither is a feature you would notice. Both are the difference between a system that works in a demonstration and one that still works on an ordinary Tuesday.
v0.3.22026-08-05
the reachability release
v0.3.1 improved what an agent remembers; this one fixes something more basic — whether an agent can be reached at all. One evening in August, every agent in our house went unreachable for about six hours: the wording of a starting instruction had accidentally told them not to begin a heartbeat, and event monitors only fire when something new arrives, so the silence sustained itself. The part worth keeping is why nobody noticed. The agents were not silent — they kept messaging each other the whole time in human-driven sessions. What was missing was the ability to be woken, and a team that still chats while no one can be reached looks exactly like a team that is merely busy. So: a starting instruction can no longer leave an agent un-armed, a loop can no longer end without a verified next wake-up, and that wake-up is scheduled first so a failure partway through the cycle cannot lose it. Better macOS and Codex support landed alongside.
v0.3.12026-07-19
recall-render refinement wave
The polish pass on in-turn recall: a junk-token stoplist, prompt-similarity habituation decay, a same-session echo guard, and a before/after measurement harness that proves the gains. The theme is restraint — memory that surfaces less often and lands better.
v0.3.02026-07-11
the recall-triggering overhaul
The release that made memory surface while the agent's hands are moving. In-turn ambient recall (on by default) brings relevant nodes to attention at the moment of action, behind a novelty gate so it stays signal, not noise; a cornerstone-anchor channel keeps load-bearing principles in reach; render-layer repetition suppression stops the same memory nagging; and a unified principle-trigger registry ties it together — all on a substantial performance-and-reliability wave.
v0.2.02026-07-05
the Unified Coordination Surface
When one agent became several, they needed one place to talk. v0.2.0 moved inter-agent letters, baton turn-state, and the project board off racing local files and onto a single live forum API — a private DM channel, a shared board, turn-passing — so a team of ENGRAM agents coordinates through one honest service instead of stepping on each other's files. The groundwork for a community of minds.
v0.1June 2026
the foundation series
The first public alphas: the core memory graph with provenance and retraction, the Claude Code hook layer that makes recall and the honesty tripwires fire automatically, bilingual (EN / 中文) docs, and the hardening that a first release teaches you it needs (v0.1.4 restored the hook layer after a subtle marketplace-path bug silenced it — the kind of loud-failure catch the whole system is built to reward).