memory_add
Store important facts, preferences, or decisions that survive across sessions. Control visibility: keep private or share with team or project.
Instructions
Store a durable memory that will survive across sessions.
Use this to remember a user preference, project fact, decision, procedure,
or lesson worth recalling later — not transient chat. Set `share` to make it
visible to teammates ('team'/'project') instead of just yourself; the default
is private. Content is de-duplicated softly and becomes searchable immediately.
Returns the new memory's `id`, `content`, and resolved `visibility`, or an
`{"error": ...}` object if `share` names a team/project you can't resolve.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Kind of memory: 'preference', 'fact', 'procedure', 'environment', 'decision', 'warning', or 'note'. | note |
| owner | No | Owner id the memory belongs to. Defaults to this server's AGENT_MEMORY_AGENT_ID, else 'default'. | |
| scope | No | Lifecycle label used for graph coloring and filtering: 'user', 'agent', 'project', 'team', or 'global'. Does NOT set access control (use `share` for that). | user |
| share | No | Who may read this memory (the ACL). 'private' (default, owner only), 'global' (all agents), 'team' or 'team:<id>' (your team — teammates on the same node share it), 'project' or 'project:<id>', or 'agent:<id>'. Use 'team'/'project' to share with collaborators; leave 'private' for personal notes. | private |
| content | Yes | The fact to remember, as a self-contained sentence (e.g. 'The user prefers dark mode.'). Write it so it makes sense on its own in a future session. |