Skip to main content
AutoSage separates chat continuity from durable recall. Long conversations remain coherent through automatic compaction, while optional durable memory carries selected facts across separate conversations.

​
Three kinds of context

ContextPurposeScope
Recent historyKeeps the latest turns verbatim, including tool-aware contextOne chat
Compacted historySummarizes older turns when a chat becomes longOne chat
Durable memoryRecalls relevant facts in future conversationsTenant, external subject, or restricted knowledge base
Compaction does not depend on durable memory. A long chat can retain continuity even when durable memory is disabled or temporarily unavailable.

​
Durable-memory settings

Durable memory is opt-in at the tenant level:
SettingValuesBehavior
modedisabled, durableEnables or disables cross-conversation memory
retentionnoneRecall may be configured, but new facts are not stored
retentionexplicit_onlyStore facts only when a user explicitly asks
retentionautomaticStore useful facts automatically and accept explicit requests
A knowledge base can narrow the tenant policy further with kbMemoryMode:
KB modeBehavior
disabledSkip durable recall and storage for this knowledge base
subjectUse the caller’s normal tenant or external-subject memory scope
kb_restrictedUse a separate memory scope isolated to this knowledge base

​
Scope by caller

CallerDurable-memory scope
Dashboard userTenant-wide memory
API end user with external_subject_idTenant plus that external subject
API-key chat without external_subject_idDurable recall and storage are skipped
Any caller on a kb_restricted knowledge baseSeparate scope for that knowledge base
Always pass the same stable external_subject_id for the same end user. This lets their memory persist across chats while keeping it isolated from every other end user served by the key.
See Tenancy for the corresponding chat-ownership checks.

​
Recall lifecycle

1

Prepare chat context

Long histories are compacted when needed. Recent turns remain verbatim and the older summary preserves decisions and prior context.
2

Resolve the memory scope

AutoSage applies the tenant policy, knowledge-base mode, caller type, and external_subject_id before any recall.
3

Recall relevant facts

Relevant durable memories are selected from the resolved scope and added as context for the current message.
4

Generate the answer

Memory context is combined with recent history, the new message, and any knowledge-base or tool results.
5

Retain new facts

When retention permits it, useful facts from the turn can be stored for future conversations.
Recall and storage are best-effort. They never block the grounded answer if memory is unavailable, and response metadata reports only a memory_used boolean rather than exposing recalled memory contents.

​
Explicit memory

When durable memory is enabled and retention is explicit_only or automatic, users can store a fact directly with phrasing such as: 
Remember this: I prefer quarterly reports as a PDF.
AutoSage confirms the memory operation instead of running a normal answer turn. Manage deletion through the memory management endpoints so changes are deliberate and scoped to the intended tenant or knowledge base.

​
Management endpoints

MethodPathPurpose
GET/tenants/:id/memory-settingsRead tenant mode and retention
PATCH/tenants/:id/memory-settingsUpdate tenant mode or retention
GET/tenants/:id/memoriesList or search tenant memories with q, limit, and offset
DELETE/tenants/:id/memories/:memoryIdDelete one tenant memory
GET/tenants/:id/memories/graphRead the tenant entity graph
GET/knowledge-bases/:id/memoriesList or search kb_restricted memories
DELETE/knowledge-bases/:id/memories/:memoryIdDelete one restricted memory
GET/knowledge-bases/:id/memories/graphRead the restricted entity graph
Memory management requires the corresponding tenant or knowledge-base access. Restricted-KB endpoints return isolated data only when that knowledge base uses kb_restricted mode. See the Tenant API, Knowledge-base API, and Memory product docs for configuration and management details.

​
Next steps

Durable memory

Choose retention and knowledge-base memory modes.

Prompt assembly

See where memory and compacted history enter a run.