At a glance
WHAT IT’S REALLY ABOUT
Building Claude agents that persist memory and improve it over time
- The workshop demonstrates the default limitation of agents: separate sessions are isolated, so information shared in one session is not available in later ones.
- Anthropic’s Memory Stores attach a persistent, file system-like store to sessions so agents can read and write information across sessions using familiar tools like bash and grep.
- Memory Stores can be configured per boundary (user/workspace/etc.), can be read-write or read-only, and can be inspected/edited manually via CLI or Console with versioned files.
- Dreaming is an asynchronous, multi-agent background job that fact-checks, consolidates, deduplicates, and reorganizes a memory store using selected past session transcripts.
- The workflow culminates in using the Dream-produced output memory store for improved recall and efficiency (e.g., index files), with options to review diffs and retire older stores afterward.
IDEAS WORTH REMEMBERING
5 ideasWithout shared memory, agents cannot carry context across sessions.
The demo shows that telling an agent information in one session doesn’t help a later session unless a shared memory store is mounted, limiting real-world multi-step workflows.
Memory Stores turn multi-session work into a cumulative knowledge process.
By attaching a file system-like store to sessions, the agent can persist notes (e.g., to a sessions.md file) and later retrieve them via tools like grep, enabling reliable recall.
Treat memory boundaries and permissions as a product design choice.
You can create many stores (per user, workspace, or other scope) and set access to read-only or read-write depending on whether the agent should be allowed to update shared knowledge.
Operational visibility improves trust and debugging.
The Console shows session activity (including tool use) and provides a memory-store file viewer; Dreaming also exposes its own session, making it easier to diagnose why certain memories were created or modified.
Dreaming addresses the “memory sprawl” problem by improving memory quality over time.
As memory stores grow, Dreaming runs a background, multi-agent harness to organize, enrich, deduplicate, and check staleness/facts so the store stays useful instead of becoming a dumping ground.
WORDS WORTH SAVING
5 quotestoday we're gonna talk a little bit about the base case with agents today, uh, which is that they're isolated, and this kind of limits their usefulness in a lot of real-world workflows.
— Kevin
a memory store is a persistent file system-like store that gives, uh-- that attaches as a resource to sessions that you create, and it gives agents access to, uh-- it gives agents the ability to read and write information across sessions.
— Kevin
the actual interesting thing here is that we've actually u- mounted it as a file system because it's such a powerful interface for the model.
— Kevin
dreaming is a, is a batch process that runs, again, asynchronously.
— Kevin
we don't actually touch the input memory store at all that you create. So this is a non-destructive process.
— Kevin
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome