Memory management requires durable memory to be enabled. If memory isn’t set up, these screens simply have nothing to show — they’ll appear empty until memories start being stored.
Tenant memories
The tenant memory screen manages the tenant-shared memory bank. It does not aggregate knowledge-base-restricted memories or the separate banks created for API end users withexternal_subject_id:
Delete individual memories
Remove any single memory you no longer want kept. Deletion takes effect immediately.
Organization members can view the tenant-shared memory bank. Only Owners and Billing admins can change memory settings or delete an entry.
Knowledge-base-restricted memories
When a knowledge base is set to KB-restricted mode, its memories are kept isolated to that knowledge base. You manage them from the knowledge base itself, with the same capabilities:- View and search that knowledge base’s isolated memories.
- Delete individual memories from it.
- Explore the entity graph for just that knowledge base.
Deletion is immediate
Removing a memory takes effect right away — the fact is no longer available for recall in future conversations. Because deletions happen here rather than mid-chat, every removal is a deliberate, auditable action.Next steps
Set up durable memory
Enable memory and choose how facts are captured.
Memory commands
Store facts conversationally from the chat.
Memory modes
Isolate memory for a specific knowledge base.
Team roles
Manage who has the admin role for memory.