86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark.

Read the report
Platform
Deploy
Solutions
Devs
Resources
Partners

AI tech talk series: Agent Memory

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.

See all AI tech talk sessions here.

34 minutes
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.
Redis

Samuel Agbede

Developer Advocate

Latest content

See all
Image
What we’ve learned building production agents: Context engineering in practice
18 minutes
Image
Inside the state of context engineering
18 minutes
Image
AI tech talk series: Context-aware apps

Get started with Redis today

Speak to a Redis expert and learn more about enterprise-grade Redis today.