Memory
Memory
Read what a workspace or a member already knows, and queue a change for the memory agent to fold in.
Memory is the standing instructions, conventions, and reference files a workspace's agents accumulate. It has two owners, and every read and write names one. A specialist is not a memory owner: what it should know lives in its own memory document and its files, on the specialist.
ownerType | Owned by | Who may read | Who may propose |
|---|---|---|---|
organization | The workspace | Any member | Members allowed by role |
membership | The member the key acts as | That member | That member |
AuthenticationRequires
memory:manage on a personal API key. A CLI session always passes.Writing memory directly is deliberately absent. The memory agent is the only writer; a proposal is a note it folds in on its next run, reconciled against everything else it knows.
| Endpoint | Does |
|---|---|
GET /v1/memory/:ownerType | The rendered memory guide and pending notes |
GET /v1/memory/:ownerType/files | List, read, and download the reference files behind the guide |
POST /v1/memory/:ownerType/proposals | Queue a change |