Webinar
Overview
An agent that forgets the customer between sessions isn’t reasoning, it’s guessing with extra steps.
Most teams patch this by stuffing more history into the context window, which works until it doesn’t: costs climb, latency climbs, and the agent still loses the thread the moment a session restarts.
This session adds Agent Memory on top of the app from session one, so context carries across turns, across sessions, and across restarts, without relying on the context window to hold everything.
We’ll show how memory is written, retrieved, and pruned, and how that’s different from just caching the last conversation.
What you’ll learn:
- Agent Memory added to the app, running across sessions and restarts.
- A working model for what belongs in memory versus what belongs in the context window.
- A look at how memory scales as more users and more sessions come online.
Speakers

Redis
Samuel Agbede
Developer Advocate
Register now
Get started with Redis today
Speak to a Redis expert and learn more about enterprise-grade Redis today.