User Memory enables agents to remember information about users across all sessions, learning preferences and context to deliver increasingly personalized interactions over time. Powered by AWS Bedrock's Agent Core Memory feature, this capability transforms one-off conversations into ongoing relationships.
What It Does
Section titled “What It Does”User Memory automatically captures and stores information about each user during conversations. This information is securely stored and seamlessly retrieved when the user returns for future conversations, enabling agents to provide contextually relevant, personalized responses without requiring users to repeat themselves.
Why It Matters
Section titled “Why It Matters”Without user memory, every conversation starts from scratch:
- Users must re-explain their role and preferences
- Agents can't adapt to individual communication styles
- Context from previous sessions is lost
- Personalization is impossible
- User experience feels impersonal and repetitive
With user memory:
- Agents remember who users are and what they care about
- Responses adapt to individual preferences
- Context builds over time
- Each conversation is better than the last
- Users feel understood and valued
What Gets Remembered
Section titled “What Gets Remembered”The system intelligently stores two types of user information:
Preferences
Section titled “Preferences”Explicit choices, settings, and stated preferences:
- Communication Style: Prefers detailed explanations vs brief summaries
- Format Preferences: Likes bullet points, tables, or narrative format
- Domain Specifics: Works in healthcare, manufacturing, finance, etc.
- Role Information: CFO, engineer, support agent, etc.
- Tool Preferences: Prefers certain tools or approaches
Semantic Understanding
Section titled “Semantic Understanding”Contextual understanding of the user:
- Domain Expertise: Level of technical knowledge
- Working Environment: Team size, company type, industry
- Interests: Topics they frequently discuss
- Goals: What they're trying to accomplish
- Patterns: How they use the system
How It Works
Section titled “How It Works”User interacts with agent
During conversation, agent notes information worth remembering
Memory automatically captured
Relevant information stored in AWS Bedrock Agent Core Memory
User returns later
Memory seamlessly loaded when user starts new session
Agent uses context
Responses incorporate remembered preferences and context
Memory evolves
Each conversation adds to and refines understanding
Personalization in Action
Section titled “Personalization in Action”Sarah's Support Experience
Section titled “Sarah's Support Experience”First Conversation (Week 1):
- Sarah asks about billing policies
- Mentions she's CFO of mid-sized manufacturing company
- Prefers detailed financial breakdowns
- Agent remembers these details
Second Conversation (Week 2):
- Sarah asks different question
- Agent already knows her role and preferences
- Immediately provides CFO-appropriate level of detail
- No need to re-establish context
Result: Faster, more relevant support
Marcus's Technical Consultation
Section titled “Marcus's Technical Consultation”First Conversation:
- Marcus asks about API integrations
- Mentions he works with Python
- Prefers code examples
- Building microservices architecture
Subsequent Conversations:
- Agent automatically includes Python examples
- References microservices context
- Provides appropriate technical depth
- No repetitive context-setting needed
Result: More efficient technical assistance
Team Knowledge Building
Section titled “Team Knowledge Building”As your organization uses the system:
- Each user builds their own knowledge profile
- New team members get immediately relevant help
- Seasoned users receive increasingly sophisticated assistance
- System adapts to individual needs and expertise levels
Configuration
Section titled “Configuration”Enable User Memory
Section titled “Enable User Memory”const agentConfig: AgentConfig = { agentId: 'support-agent', agentName: 'Customer Support Agent', userMemory: { enabled: true, strategies: ['preferences', 'semantic'], maxMemorySize: 5000 // tokens }};Customize Memory Strategies
Section titled “Customize Memory Strategies”Control what gets remembered:
userMemory: { enabled: true, strategies: ['preferences'], // Only explicit preferences
// Or both: strategies: ['preferences', 'semantic'], // Full memory
retentionDays: 90 // Clear after 90 days of inactivity}Per-Chat App Configuration
Section titled “Per-Chat App Configuration”Different settings for different apps:
// Customer support: remember preferencescustomerSupportAgent: { userMemory: { enabled: true, strategies: ['preferences'] }}
// Technical assistant: deep semantic understandingtechAssistant: { userMemory: { enabled: true, strategies: ['preferences', 'semantic'], maxMemorySize: 10000 // More context for technical work }}Use Cases
Section titled “Use Cases”Customer Support
Section titled “Customer Support”Remember customer context:
- Previous issues and resolutions
- Product preferences
- Communication style
- Account history
Benefit: Customers don't repeat themselves
Technical Assistance
Section titled “Technical Assistance”Adapt to developer expertise:
- Programming language preferences
- Framework choices
- Complexity level appropriate to skill
- Project context
Benefit: More relevant technical guidance
Sales Assistance
Section titled “Sales Assistance”Personalize recommendations:
- Budget constraints
- Feature priorities
- Decision criteria
- Purchase history
Benefit: Better product recommendations
Internal Knowledge Base
Section titled “Internal Knowledge Base”Tailor information delivery:
- Department and role
- Areas of responsibility
- Information preferences
- Access patterns
Benefit: Faster information discovery
Privacy and Security
Section titled “Privacy and Security”User Control
Section titled “User Control”Users own their memory:
- Can request to view stored memory
- Can ask agent to forget specific information
- Can clear all memory
- Transparent about what's remembered
Entity Isolation
Section titled “Entity Isolation”Memory respects organizational boundaries:
- External users: memory scoped to their entity
- Internal users: broader but controlled access
- No cross-entity memory leakage
- Secure isolation guaranteed
Data Protection
Section titled “Data Protection”Secure storage and handling:
- Encrypted at rest in AWS Bedrock
- Not used for AI model training
- Subject to retention policies
- Audit trail of memory access
Best Practices
Section titled “Best Practices”Start Conservative
Section titled “Start Conservative”Begin with limited memory:
- Phase 1: Enable preferences only
- Phase 2: Monitor what gets remembered
- Phase 3: Add semantic understanding if beneficial
- Phase 4: Adjust based on user feedback
Set Appropriate Retention
Section titled “Set Appropriate Retention”Match retention to use case:
- Customer support: 90-180 days
- Internal tools: Longer retention (1+ year)
- Sensitive domains: Shorter retention
- Consider regulations: GDPR, data protection laws
Educate Users
Section titled “Educate Users”Make memory transparent:
- Explain what gets remembered
- Provide examples of benefits
- Show how to manage memory
- Build trust through transparency
Monitor and Refine
Section titled “Monitor and Refine”Continuously improve:
- Review what's being remembered
- Identify useful vs noise
- Refine memory strategies
- Measure personalization quality
Advanced Features
Section titled “Advanced Features”Explicit Memory Commands
Section titled “Explicit Memory Commands”Users can directly instruct memory:
"Remember that I prefer technical explanations" "Forget my previous project context" "What do you remember about me?"
Memory Inheritance
Section titled “Memory Inheritance”Share memory patterns:
- Team memory profiles
- Role-based defaults
- Department preferences
- Organizational standards
Memory Analytics
Section titled “Memory Analytics”Understand memory usage:
- Most commonly remembered facts
- Memory utilization per user
- Personalization effectiveness
- Privacy compliance metrics
The Learning Advantage
Section titled “The Learning Advantage”User Memory creates a continuous learning cycle:
- First Interaction: Agent learns basic information
- Subsequent Interactions: Context deepens
- Preferences Refined: Understanding improves
- Anticipatory Service: Agent predicts needs
- Relationship Deepens: Each conversation better than the last
This transforms AI assistants from tools into knowledgeable colleagues who understand your team's unique needs and working styles.
Getting Started
Section titled “Getting Started”Enable User Memory
Configure memory strategies for your agents.
See Memory in Action
Experience personalization in the Weather Sample.
Understanding Memory
Deep dive into memory architecture and privacy.
Related Capabilities
Section titled “Related Capabilities”Session Management
Conversations persist with full history alongside user memory.
Advanced Chat Apps
User memory enhances the chat experience.
Multi-Tenancy
Memory respects entity boundaries for secure isolation.