Memories and search

Memories are saved facts that help Copilot carry useful context into later work. A memory can be private to its owner or explicitly shared with the organization. Org Brain indexes eligible shared content and adds cited organizational answers; it is separate from the saved Memory list and Studio’s unified search.

​

Save a useful Memory

Ask Copilot to remember a specific, verified fact. State its audience explicitly:

• “Remember privately that I prefer maintenance summaries in UTC.”
• “Save this for the organization: the Melbourne router maintenance window is Sunday 02:00–03:00 UTC, verified against change CHG-123.”

The AI Memory create tool defaults to private. Organization-wide saves need explicit approval. Read the proposed content and audience before accepting, and confirm the save succeeded. Include the customer, site, system, and verification date when they matter. Update an existing fact when reality changes instead of saving contradictory copies.

​

Inspect, edit, and delete

Open AI Memories from Studio’s navigation or search. Search memories filters the saved records by content, category, and tags. Open a record to inspect its content and visibility, make a correction, or delete it. The list also supports selecting multiple records for deletion. Categories and tags help distinguish topology, incidents, configuration, procedures, and other operational context. A credential hint may name the Key Chain entry to use; it must never contain the credential value. Private-to-organization visibility changes depend on the available sharing controls. If Share with organization is unavailable, ask Copilot to save an explicit organization-wide record and review its approval instead of assuming the private record was published.

​

Private and shared context

Private Memory is not organization-wide knowledge. In your own Personal conversation, Copilot can use the private memories you are authorized to access. In a shared channel or conversation, Memory context is limited to explicitly organization-visible records so private facts do not enter replies read by other people. Private Memory access depends on supported client and server authorization. Keep Studio current, and treat an unavailable private-memory operation as unavailable rather than assuming it synced. Private visibility is an access rule, not a promise that the record exists only on one device.

​

Organization work-product records

Copilot can save structured organization-visible records for facts and work products: apps, artifacts, repositories, workspaces, deployments, and services. A record can carry a stable subject identity, title, summary, last-known state, locator, host, session, workspace, revision, and tags. Ask it to update the same subject after a change:

Verify the WAN dashboard’s current deployment, then update its existing organization record with the revision and location.

Reusing a stable identity, such as an application’s absolute workspace path, keeps later chats attached to the existing work instead of a new duplicate. These records remain saved Memory; Org Brain can make eligible records available as cited evidence.

​

Choose the right search

Unified search can use names, text, metadata, and semantic relevance across supported Studio resources. Search before creating another host, procedure, Memory, or app so you preserve its identity and history. For example, search a hostname or site code to find a target; an artifact title or workspace path to resume work; or a command such as settings, usage, or key chain to navigate.

​

Cited answers and freshness

When enabled, Org Brain can answer questions about shared memories and other permitted sources. Ask a bounded question and inspect the Sources in its answer card. A Memory citation opens the current authorized source, which may have changed after the answer was written. Saving a Memory does not guarantee immediate indexing. After an edit, ask again when the source has updated. After deletion, its old citation can become unavailable; the earlier answer remains historical chat content. See Org Brain for source availability, consent, and access limits.

​

What not to store

Keep passwords, tokens, private keys, recovery codes, and session cookies in Key Chain. Do not save unverified AI conclusions as established fact or use Memory for rapidly changing values that should come from a live system. Store a full transcript or report as its appropriate conversation or artifact, then save only the durable lesson. Review shared memories periodically. Correct stale claims, remove duplicates, and distinguish historical findings from current state. Organization-memory metadata is sanitized before persistence, but titles, summaries, tags, and locators still need the same care.

​

Related