Shared memory
Keep durable context across assistants while retaining control over changes.
Sections in this article
Enable only the scope you need
Memory is off by default. When enabled, use Global, Workspace, or Team memory according to where a fact belongs. Do not put a project-only convention into Global memory.
Memory is local shared context, not a cloud account sync or a transcript archive. Store concise durable preferences and facts rather than secrets or entire conversations.
Ask an Assistant to remember
Explicitly ask a tool-capable Agent Assistant to remember a fact. It interprets the request and calls the memory tool; only a successful save makes the memory available in the same scope.
Ambiguous requests need clarification. Inferred suggestions and conflicting changes require review. Teams currently read memory but do not write it; model-only Chat Assistants receive injected memory but cannot directly save it.
Review and change memory
You can directly edit or delete saved memory. Review proposed additions, updates, or deletions in Pending changes and accept or reject the proposed group.
Memory suggestions are an independent optional feature. Background organization processes new conversation material after idle time, without automatically overwriting or permanently deleting existing memory. Deleting a memory does not retract content an external Agent has already received.