Skip to main content

​
What context is

Context is the material AI SRE can reuse across troubleshooting sessions. It has two parts, each with its own page under the Context group of the AI SRE → Customize sidebar.
  • Knowledge is maintained by people. It describes how this environment runs: a guide named DUTY.md, plus runbooks, service lists, and similar files. A session reads the guide first and opens the other files when it needs them. Entry: AI SRE → Customize → Context → Knowledge.
  • Memory is organized by the system. After a session, it keeps preferences, procedures, facts, and lessons that will still matter later. You can also ask, in the conversation, to remember or forget something. Entry: AI SRE → Customize → Context → Memory.
Both pages have an input box at the bottom. Describe what to change, and the console opens a new chat. The AI explains the change first and saves it after you agree.

​
Three scopes

Both kinds of material are organized by scope, but they support different scopes. Personal scope has no knowledge. Shared scope has no memory.

​
Scope and permissions

Everything under Customize (skills, knowledge, MCP, agents, environments) uses the same two-level scope: shared (account level) and team. The account is the security boundary. A team only marks ownership and edit rights. A resource the list doesn’t show is the same when opened by ID: the MCP, A2A Agent, and Skill detail pages, and Skill downloads, report that the resource does not exist rather than revealing that the ID exists. For troubleshooting that spans teams, ask the other team to set the relevant resources to shared.

Learn about Knowledge

How the guide, runbooks, and files are organized, and how the assistant reads them in a session.

Learn about Memory

How memory is gathered from conversations, what personal and team scopes each show, and how to edit or delete a file on the page.