AI agent long-term memory with memory bank
This item is no longer on the current shelf. Its page remains available, and editorial corrections may be made. See what is featured now.
Why it earned a slot
Google Cloud Tech describes using ADK Memory Bank to save and retrieve context across conversations. Its published outline separates SessionService from MemoryService and covers PreloadMemoryTool and semantic retrieval. For an agent that needs durable preferences, I would test whether a new session retrieves an explicitly saved preference while keeping another user's memory separate. Creator video and chapter outline.
The short version
Conversation history and cross-session memory need different checks.
Why it matters
The creator describes saving information across conversations and retrieving relevant facts with ADK memory tools. That scope is useful when a session ends but a permitted preference should remain available.
My take
I would start with a small set of explicit preferences, then check retrieval in a separate session and isolation between users before connecting this to a production agent.
How it connects
- Treat retaining a conversation and retrieving a relevant fact as separate requirements.
- A memory feature needs an explicit policy for what is saved and who may retrieve it.
Bottom line
Use a cross-session retrieval and user-isolation test to decide whether this approach fits your agent.
Historical Brendon Score: 7.7/10
Recorded for a previous shelf selection. Editorial corrections do not constitute a new assessment.
Show the math
- Quality: 7.5/10 — base
- Authority: 7.0/10 — +0.20
- Freshness: 1.0/10 — +0.00
- Engagement: 2.5/10 — +0.00
- Relevance: 9.0/10 — +0.00
- Total: 7.7/10
Why this is here
Checks cleared:
- On-topic for the shelf
- Specific, non-clickbait title
- Source authority 7/10
- Embeddable
