Anders Swanson wants agents to stop forgetting the work they just did. The Oracle AI Database developer advocate told AI Engineer that context windows are not memory, they are input for the current run, and every synthesis gets tossed when the session ends.
The fix he demoed is a governed memory layer invoked as a function by the agent runtime via hooks, MCP or skills. Swanson laid out the loop: an agent does work, a distilled fact is redacted, enriched, embedded and stored, then a later session reconstructs context by retrieving that fact. Storage is typed, episodic slices of transcripts, semantic facts, procedural routines and short lived working state, each with IDs, text, JSON, vector and text indexes, graph edges, temporal validity and audit events. Recall is hybrid by design, fusing vector similarity, lexical search, relational entity lookup, graph traversal and signals like recency and feedback scores with weights and re-ranking to build a scored context card.
That persistence is also the attack surface.
Swanson walked through how it breaks. Poisoned memory is the worst case, a remote, untrusted source plants a durable instruction via prompt injection when redaction, scoping and review are missing, then every future retrieval spreads it. Data leakage is the quieter sibling, stray PII or secrets slipping in before embedding. Bad scoping leaks memory across tenants or users on both write and read, stale memories push deprecated procedures like an old npm workflow, conflicts surface when two memories rank highly for the same task, and over recall crowds out signal as the store grows to tens of thousands. He said feedback must close the loop, promoting helpful memories and demoting stale or harmful ones, with lifecycle, approvals and suppression built in. No patch fixes this. It requires governance before the write.
Swanson framed files and scratch pads as workarounds that do not scale, grep helps but not as hybrid retrieval, and if you keep extending files you end up rebuilding a database. That is his pitch for a multi-model database that can hold rows, vectors, full text, graphs and episodes behind one connection. It contrasts with how others package memory today. Hermes Agent, for example, splits memory into three practical layers, durable memory for stable facts and preferences, skills for reusable procedures, and session search for past conversations, while the open source agentmemory project from rohitg00 pairs persistent memory with code graph indexing and knowledge graphs across docs and media to keep coding agents oriented.