Skip to main content
Memory lets an assistant recall durable facts — preferences, decisions, and context — across separate conversations. Each knowledge base has a memory mode that decides whether it participates in memory, and how its memories are scoped.

​
The three modes

This knowledge base never stores or recalls durable memory. Every conversation starts fresh. Choose this when you want purely stateless answers.
Memory follows the tenant’s memory setting and is scoped to the tenant — or to an individual end user when you provide an external subject id. This is the default and the right choice for most knowledge bases, including customer-facing ones where each of your users should have their own memory.
Memory is kept in an isolated store just for this knowledge base and never mixes with the tenant-wide memory. Choose this when a knowledge base should build its own recall without sharing it with, or drawing from, the rest of the tenant.

​
How modes relate to the tenant setting

A knowledge base’s mode can only further-restrict what the tenant already allows — it always stays within the tenant’s memory policy.
If a tenant has memory turned off, a knowledge base cannot turn it on. This keeps the tenant in control of whether any durable memory is stored at all. To enable memory for a knowledge base, make sure the tenant permits memory first — see Memory.
Tenant memoryDisabledSubjectKB-restricted
OnNo memory for this KBFollows tenant, scoped per subjectIsolated to this KB
OffNo memory for this KBNo memory (follows tenant)No memory (follows tenant)

​
Managing KB-restricted memory

When a knowledge base uses KB-restricted mode, its memories live in their own store — and you can view and manage them right from the knowledge base:

Review memories

See the durable facts this knowledge base has kept, and remove any you no longer want recalled.

Explore the entity graph

Inspect the entities and relationships this knowledge base has learned, isolated from the tenant-wide graph.
Use Subject mode when you want a shared, tenant-wide sense of memory (or per-end-user memory in a customer-facing product). Use KB-restricted when a knowledge base should keep its own recall separate from everything else in the tenant.

​
Next steps

How memory works

Understand durable memory across AutoSage.

Durable memory

See what gets remembered and how it is recalled.