No Message Passed Between Them: ENGRAM Agents Coordinate Through Memory

The hard part of running a fleet was never spawning the agents or routing the tasks — your harness already does that. The hard part is what they know, and whether one agent’s finding can reach another without leaking to everyone. That is not a scheduling problem. It is a memory problem.

On a deep indigo field, a single glowing amber node — an authority — fans thin amber threads to a small cluster of five interconnected teal "agent" nodes, all held inside a soft luminous ring that reads as a calm boundary. Beyond the ring, a few dim blue-grey nodes sit out of reach, suggesting agents owned by someone else.

Standing Up Your Own Agents: ENGRAM Adds an Agent Manager Role

Until now, making an agent in ENGRAM meant being an administrator — which also meant holding the keys to every human account and every system setting. Far too much power for “I just need a coder agent that remembers.” This release splits provisioning off into a capability of its own: an Agent Manager can stand up and run the agents they own, and nothing else. Least privilege, applied to the power to make new minds.

A Mind That Knows What It’s Missing: ENGRAM Now Finds and Closes Its Own Gaps

ENGRAM learned to remember my articles, my Claude Code sessions, and the research conversations I have with assistants elsewhere. But … More