Docs / Agents
Memory and playbooks
Keep durable facts and verified procedures for your agents, with a clear personal or team scope.
Memory gives future agents reusable facts and procedures, so they don't live in only one transcript. Ask an agent to remember a stable decision or to correct an outdated fact. Don't use memory as a live inventory or a place for credentials.
Personal and team scope
- Personal memory holds facts and preferences that are yours.
- Team memory holds shared system facts, operational decisions and findings your teammates can see.
- Playbooks capture a team procedure after it has worked and been verified. A guess or an unfinished plan is not a playbook.
Say the scope when you ask to save something. For example: "Remember for the team that staging deploys use the release workflow," or "Remember that I prefer short incident summaries." Never include passwords or tokens.
Retrieval is explicit
An agent saves and searches memory with tools. The whole memory store is not added to every new prompt. A clear title and concrete keywords make a fact easier to find later. Ask the agent to look up a past decision when you want it reused, and check old facts against the current state before making changes.
Review and correct
Open Settings → Memories to see the saved records. Team members can review and remove shared team memories. Remove anything that shouldn't be kept. When a fact changes, ask the agent to save a corrected record that replaces the old one, rather than a conflicting duplicate.
Deleting a memory does not erase the conversation it came from, or undo work done with it.
Instructions set standing guidance, skills define procedures, and memory records what was learned. See Instructions and Skills.