Cross-Session Memory

Problem

Per-thread memory loses everything between sessions: every new conversation starts from a blank slate, the user has to repeat themselves about basic facts, and the assistant feels amnesic and impersonal. The team needs a mechanism that captures the right kind of information at the right time, stores it durably across sessions, and surfaces it back into context when relevant — without leaking private details, blurring sessions together, or storing every passing remark as if it were load-bearing.

Solution

Maintain a per-user store of distilled facts (preferences, prior context, names, projects). Load relevant slices into each session's context. Provide explicit add/forget tools. Audit and surface memory entries to the user. Deletion controls and a user-visible memory inspector (delete / disable / export) satisfy regulatory and trust requirements.

When to use

• Per-thread memory loses important user-specific facts between sessions and the assistant feels amnesic.
• A per-user store of distilled facts can be maintained with audit, deletion, and forget controls.
• Loaded memory slices meaningfully improve responses across sessions.