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.
Tag: openai
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 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.
A Framework for Testing Agentic Design Patterns Using LangChain & LangGraph
This blog describes a Python application built using LangChain and LangGraph frameworks for testing agentic workflow design patterns such as … More