Overview
When enabled, Agent Memory automatically:- Extracts facts from conversations (preferences, issues, context)
- Stores memories per user across all their conversations
- Retrieves relevant memories when responding to provide context
- Updates memories when information changes
Use Cases
Customer Support
- Remember past issues and resolutions
- Track customer preferences (communication channel, timing)
- Maintain context about subscription level or account type
Personal Assistants
- Remember user preferences and habits
- Track ongoing projects or tasks
- Maintain context about user’s situation
Enabling Agent Memory
Via Admin Interface
- Navigate to AI Studio → Agent Memory
- Toggle Enable to activate memory
- Configure the number of memories per conversation (1-100)
- Optionally customize memory categories
ℹ️ NOTE: Agent Memory can also be configured via API. See the Public API v1 Reference for endpoint details.
Configuration Options
Memory Categories
Memories are automatically categorized to help organize and retrieve relevant information:Default Categories
Customizing Categories
You can customize the memory categories to match your use case:- Navigate to AI Studio → Agent Memory
- Enable memory if not already enabled
- Edit the Memory Categories section
- Define your custom categories in markdown format
- Click Save Categories
How It Works
Memory Extraction
After each conversation, the system:- Analyzes user messages for extractable facts
- Categorizes facts based on defined categories
- Compares with existing memories
- Adds new facts, updates changed ones, removes outdated ones
Memory Retrieval
When a user starts a conversation:- System retrieves all memories for that user
- Most recent memories are prioritized
- Memories are included in the agent’s context
- Agent uses memories naturally without explicitly mentioning them
Memory Lifecycle
Best Practices
Do
- Start with defaults - The default categories work well for most support scenarios
- Be specific - Custom categories should have clear, non-overlapping definitions
- Test extraction - Review extracted memories to maintain quality
- Set appropriate limits - More memories = more context but higher token usage
Don’t
- Over-customize - Too many categories can confuse the extraction
- Store sensitive data - Avoid extracting PII or sensitive information
- Ignore privacy - Make sure users know their information is being remembered
Privacy Considerations
Data Storage
- Memories are stored per user and per tenant
- Memories are associated with the user’s unique identifier
- All memory data follows your tenant’s data retention policies
User Control
Consider implementing:- User-facing memory management (view/delete their memories)
- Clear communication about what information is remembered
- Opt-out mechanisms where required
Compliance
- Review memories for compliance with GDPR, CCPA, or other regulations
- Implement data retention policies for memories
- Provide data export/deletion capabilities as required
Troubleshooting
Memories Not Being Extracted
Memories Not Being Extracted
- Verify memory is enabled in settings
- Check that conversations have sufficient content
- Review extraction model configuration in the admin interface
Irrelevant Memories Retrieved
Irrelevant Memories Retrieved
- Consider reducing the maximum memories per conversation setting
- Review and customize category definitions
- Delete outdated or incorrect memories via the admin interface
High Token Usage
High Token Usage
- Reduce the maximum memories per conversation setting
- Review if all categories are necessary
- Consider more specific category definitions
Related
- Agents — Agent configuration reference
- Agent Best Practices — Design patterns
