store_memory
Capture and store durable memories such as user preferences, project entities, or solved cases. Use to persist important information across sessions.
Instructions
Store a durable memory when the user shares a stable preference, identity fact, project entity, reusable pattern, or solved case that should survive future windows. Do not use this for transient task state; use it only for memory worth keeping.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Memory text to store | |
| category | No | Durable memory category | events |
| importance | No | Importance score from 0 to 1 | |
| scope | Yes | Required scope such as project:recallnest or session:abc123 | |
| source | No | How this memory was captured | manual |
| tags | No | Optional tags | |
| canonicalKey | No | Optional stable key for merge/update semantics | |
| topicTag | No | Optional topic tag for intra-scope partitioning (e.g. 'auth', 'deploy', 'testing'). Auto-detected if omitted. | |
| privacyTier | No | Privacy tier: ephemeral (auto-expire, no KG), private (persist, no KG), durable (default), shared (cross-scope) | durable |
| validUntil | No | Optional expiration: ISO date string or ms timestamp. Memory will be deprioritized after this time. | |
| eventTime | No | Optional event time: when the event actually happened (ISO date or ms), distinct from storage time. | |
| confidence | No | Optional confidence override: number (0-1) or {score, reliability}. Auto-assigned from source if omitted. |