Most agents start every conversation from zero. This walkthrough shows how memory stores and dreaming let them carry knowledge across sessions — and keep it clean over time.
On Claude Managed Agents, you usually run one session at a time. A session is a single, ephemeral conversation thread. By default, nothing carries over: what you tell one session is invisible to the next.
Try it. Tell the left session a fact, then ask the right session to recall it.
Just like people, agents need somewhere to store what they learn and read it back later. That shared place is a memory store.
A memory store is a persistent, file-system-like store. You create as many as you like and decide the boundaries — per user, per workspace, per org. It mounts onto a session's container as a real filesystem.
Mounting it as a filesystem is the clever part: the agent gets powerful, familiar tools. It can ls and bash to explore, grep for keywords, and read or write files — far more useful than a flat blob.
Now repeat the same test — but this time both sessions share one store. Watch the agent check memory first, write to it, then recall from it in a later session.
sessions.md, and answered using knowledge it was never directly told. Memory transferred across sessions.Memory files are also versioned — every edit creates a new version. You can list files, inspect them in a console viewer, hand-edit them, or add memories manually.
Left alone, agents dump into the store. It grows unbounded, fills with duplicates, and goes stale. Dreaming is an async batch job that fixes this. You give it an input memory store plus a batch of session transcripts; it runs a multi-agent harness over them.
An orchestrator spawns one sub-agent per session. Each sub-agent fact-checks, enriches with dates and identifiers, then the system consolidates duplicates and organizes files. It's exhaustive by design — Claude reads everything so it misses nothing.
Press play to run a dream. The orchestrator kicks off sub-agents, the token counter climbs, then it writes results to a fresh output store.
It runs asynchronously for minutes to hours — never live while agents work. Because it's built on the same session primitives, you can click into the dream's own session and watch exactly what it's doing.
Everything stacks. Each layer adds capability without replacing the one below. Tap each to expand.
One isolated agent run — a single conversation, typically ephemeral.
Connects information across sessions — a shared filesystem they read and write.
Organizes, enriches, and de-stales the store over time so it never blows up.
If this resource maps to a real bottleneck on your team, ask Tomer about a Claude Code workshop. The fit check is short: team size, current Claude usage, main bottleneck, and timing.