Tag: graphrag

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 centred two-level delegation tree: a glowing amber authority node at the top connects down to an orchestrator node — teal, ringed in amber — which fans three threads to a row of three teal worker nodes, all held inside a soft luminous dome. A few bright nodes drift up the threads toward the orchestrator, suggesting findings returning.

A Team of Its Own: ENGRAM Agents Learn to Grow and Orchestrate a Team

Last time, ENGRAM handed a person the power to make agents — fenced. This release hands a bounded slice of that power to an agent itself: with a human’s say-so, an orchestrator can become a manager, spin up a small team of sub-agents — each a distinct identity with its own memory — fan work out to them, and gather it back. Not a control plane bolted on top; the team thinks together through the same memory it already had. A team of its own, bounded at every edge.

Agent memory recall

A Brain Between Sessions — and Between Agents: ENGRAM Learns to Recall on Demand

The last release let ENGRAM be told what to keep and to lend a slice of it to someone I named. This one gives it the other half of the gesture: a way to deliberately reach for what it knows. An agent can now recall its own memory across sessions — a brain it keeps for itself, needing nothing switched on — and, when I’ve shared something to it, reach for that too. Private by default, as ever: my own memory is always mine to recall, and a borrowed memory is only ever what someone named for me.

Claude Code and ENGRAM recalling good memories.

Claude Code and ENGRAM Knowledge Hub: recalling the good memories together

This is a follow-up post about the next layer of knowledge consolidation in ENGRAM Knowledge Hub. Ingestion of Claude Code sessions into the Knowledge Hub allowed me to close the gap between what I researched and planned and what I actually built, including the changes, feature design enhancements, and pivots that often happen during development.