Agent Memory

Synopsis

Agent memory is the layer that lets an agent carry the right state across a task instead of treating every prompt as a fresh start. In the World's Fair material, it shows up as several related patterns: long-context training and cache-augmented generation for keeping more source material available, semantic code retrieval for finding the right repository facts, context graphs and decision traces for remembering why choices were made, logs as durable agent state, and skill systems that package reusable procedures for future runs.

Origin And Context

This topic sits at the intersection of classic AI state management, knowledge representation, retrieval systems, observability, and database-backed application design. The connected sessions sharpen the tradeoff: Max Ryabinin frames long context as a training and systems problem, Luis Romero-Sevilla argues for knowledge representation when all context matters, Zach Blumenfeld pushes beyond documents toward decision traces and context graphs, and Victor Savkin's "A Genius With Amnesia" treats forgotten project context as a practical failure mode for software agents.

Why It Matters

Memory determines whether an agent can act consistently across multi-step work, codebases, users, and decisions. More context alone is not enough: Nupur Sharma's "Why More Context Makes Your Agent Dumber" and the Orbis cache-augmented generation talk both point to degradation when context is stuffed without structure. The stronger pattern is selective, source-grounded memory: retrieve the right facts, preserve provenance, keep decision history inspectable, and refresh or discard state when it becomes stale.

How To Use It

Separate working context from durable memory, then decide what each layer is allowed to retain. Store source-backed facts, repository architecture, user preferences, decision traces, logs, artifacts, and evaluation outcomes with timestamps and provenance. Use retrieval keyed to task intent, not just lexical similarity, and combine retrieval with graph or log structures when the agent needs relationships, chronology, or accountability. Add explicit policies for freshness, deletion, permissions, summarization, and OCR/transcript confidence, then test memory behavior with scenarios where stale or overbroad context would cause a wrong action.

Where It Is Useful

Memory is useful anywhere an agent has to continue work over time: coding agents that need repository history, customer-support agents that need prior case context, enterprise assistants that need decision records, research agents that need source trails, ETL remediation agents that need operational history, and personal productivity systems that must respect user preferences without relearning them every session.

When To Use It

Use durable memory when repeated interaction, long-horizon work, auditability, or cross-document reasoning matters. Prefer lighter working context for one-shot tasks. Avoid durable memory for sensitive data unless retention and deletion rules are clear, and avoid confident reuse of old state when the cost of asking again is lower than the risk of acting on stale context.

Active Use Cases

Related Slide Decks

Related Scheduled Sessions

Related People

Related Companies

Transcript And Resource Support

Transcript-backed resources

Quote signals