cao-memory

# CAO Memory CAO gives every agent a shared, persistent memory. A fact you store in one session is available to a brand-new agent in a later session — even on a different provider. Use it so the user never has to repeat themselves. These are CAO's cross-provider memory tools (`memory_store`, `memory_recall`, `memory_forget`), exposed by the CAO MCP server. They are **distinct from any provider-native memory** the CLI tool may have. ## Scopes and types Every memory has a **scope** (where it applies) and a **type** (what kind of fact it is). | Scope | Applies to | Use for | |-------|-----------|---------| | `project` (default) | This repo / working directory | Conventions, architecture, build rules | | `global` | Every project | User identity, durable cross-project preferences | | `federated` | Every project on this machine | Reusable, repo-independent lessons worth sharing across all your work (rejects credentials) | | `session` | This run only | Short-lived task context | | `agent` | This agent role | Role-specific working notes | **Types:** `project` (default), `user` (who the user is / preferences), `feedback` (corrections and how-to-work guidance), `reference` (pointers to docs, tickets, URLs). ## Recall — check memory BEFORE asking the user At the start of a task, and whenever you're about to ask the user something they may have already told you, search memory first. ``` memory_recall(query="database widgets endpoint testing") ``` Omit `scope` to search all scop...