Agent Memory

Shared agents need a different harness: action-boundary security, selective group memory, per-user privacy, and routing that decides both who receives information and when the agent should speak.

UniMem routes novel experience into retrieval memory and consolidates recurring patterns into expandable parameters, offering a design for agents that learn across unlabelled task streams.

MemLens scores individual agent memories, stores them by value, and exposes quality, latency, and token tradeoffs—an inspectable alternative to retaining every interaction equally.

Netflix’s performance-agent playbook feeds production profiles and exact deployed code to agents, then relies on canaries and engineers to validate proposed optimizations.

A delayed KV-eviction policy helps when memory reuse is sharp and observable, but loses its edge on natural-text benchmarks—a useful warning for agent-memory claims.

LLM synthesis breaks simple source pointers when facts merge, change, or outlive one input. Model provenance inside the context graph so agents can filter trust, debug derivation, and apply deletion policies.

Atlan’s agent experiments argue for shared, versioned context instead of per-agent memory: a portable layer for business facts, skills, norms, retrieval, and feedback across changing harnesses.

An open-source memory hub turns agent conversations, workflows, docs, and code into governed assets that can be reused across sessions and roles, reducing repeated project setup.

A 100-person factory built a multi-agent sales system around organized company memory, specialist roles, and human approval. The useful pattern is retrieval and governance, not custom model training.

eve’s Chat SDK channel lets one agent span messaging adapters while retaining threads, approval cards, proactive sends, webhook handling, and overridable defaults.

Anthropic's harness pattern for multi-session agents: an initializer sets up the env, a JSON feature list, and progress files; each session then ships one feature, verified end-to-end and committed to git.

ECC packages skills, hooks, memory, orchestration, and security controls for multiple coding-agent harnesses, but its breadth makes selective installation and verification essential.