Overview
A new session starts from the memory files already in the current scope. Without memory, you’d re-explain your habits every time: where to look first for a kind of failure, or why you dropped an earlier approach. Every investigation would start with the same background. Memory keeps those points as Markdown files and later sessions reuse them. Memory is not knowledge. People maintain knowledge, and it describes how the environment runs. The system organizes memory: preferences, procedures, facts, and lessons kept from conversations. Both belong to the console’s Context group, but each has its own page: AI SRE → Customize → Context → Memory.Memory types
Each memory file starts with a name, a one-line description, and a type. There are four types:
Where the file is saved follows the session. A session bound to a team writes that team’s memory. A session with no team writes your personal memory. A memory stays until you change or delete it.
How memory is created
Memory arrives in two ways:- You ask for it. In the conversation, tell the assistant to remember, change, or forget something. It writes or updates the matching memory file.
- After the session. When a session ends, the system keeps what will still be useful later.
How the Agent uses memory
When a session starts, the memory files in the current scope are ready. The assistant sees each file’s name and description first, and opens the body when it needs the detail. A session bound to a team uses that team’s memory. A session with no team uses your personal memory. The four types carry different weight: procedure, fact, and lesson are past records that must be checked against the current situation before use. Preference is a request you made explicitly, followed within its stated scope, and it wins when it conflicts with a Skill’s or tool’s default behavior.Scope & isolation
Memory has only two scopes, Personal and Team. There is no account-level memory.- Personal memory: readable only by the person it belongs to.
- Team memory: readable when the current session is bound to that team, or when the reader is a member of that team. Account owners and admins get no exemption, and there is no cross-team read.
View and edit it in the console
Go to AI SRE → Customize → Context → Memory.- Pick a scope: switch between Personal and Team at the top; for Team, pick one of your teams from the dropdown. There is no Shared (account-level) memory.
- Find a memory: the list on the left is grouped by Preference / Procedure / Fact / Lesson, newest update first within each group. The search box filters by name, description, and file name.
- Edit: click Edit on the right, change the name, the one-line description (when it applies), and the content, then save. This page has no create entry — memory is produced only in a conversation (see How Memory Is Created). The type cannot be changed here either, because it is fixed when the memory is written. The page only groups by type and writes the type back unchanged.
- Delete: after deletion, later conversations no longer use it. Telling the assistant to forget something in the conversation has the same effect.
Ask AI to change it
With edit permission, an input box sits below the body (placeholder: “What should change? for example, make the release window weekdays 10:00 to 16:00”). After you send it, the console opens a new chat whose input already holds a reference to this scope’s memory and your request. Personal memory opens a personal session, and team memory opens a session bound to that team, because memory is written only to the session’s own scope. Once sent, the AI first explains in text which memories it will add, merge, or delete, and saves only after you agree.Related pages
Learn about Context
How memory and knowledge differ, and what personal, team, and shared scopes each contain.
Learn about Knowledge
The guide and runbooks are maintained by people. They are not the same material as memory organized by the system.