Skip to main content
Memory gives future agents reusable facts and procedures without keeping them only in one transcript. Ask an agent to remember a stable decision or correct an outdated fact; do not use memory as a live inventory or a store for credentials.

​
Personal and team scope

  • Personal memory holds facts and preferences specific to the member.
  • Team memory holds shared system facts, operational decisions and reusable findings visible to teammates.
  • Playbooks capture a reusable team procedure after it has actually worked and been verified. A guess or an unfinished plan is not a verified playbook.
Specify the scope when asking to save something. For example: “Remember for the team that staging deploys use the release workflow,” or “Remember my preference for concise incident summaries.” Never include passwords or tokens.

​
Retrieval is explicit

An agent saves and searches memory through tools. The complete memory store is not automatically placed into every new prompt. A useful title and concrete keywords make a fact easier to retrieve later. Ask the agent to look up a past decision when you want it reused, and verify historical facts against current state before making changes.

​
Review and correct

Open the team’s Settings → Memories to inspect available records. Team members can inspect and remove shared team memories. Remove material that should not be retained. For a changed fact, ask the agent to save a corrected record that supersedes the old one rather than creating conflicting duplicates. Deleting a memory does not erase its original conversation or undo work done using it. Instructions define recurring guidance; skills define procedures; memory records what was learned. See Skills.