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.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).