remember
File a concept, decision, or finding as a memory node. Search first to prevent duplicates; review suggested connections after creation.
Instructions
File a concept, decision, or finding. Use this for a single entry only — prefer remember_all for batches — and always search first to avoid creating a duplicate. Before filing, consider whether a similar memory already exists. If so, suggest linking to it with connect rather than creating a duplicate. Duplicate nodes with no edges are the most common cause of drift candidates. Use transient=true for ticket state, sprint notes, or any node expected to become stale within days. Transient nodes are candidates for archiving once the related work is complete. The response includes a suggested_connections field — review these and call connect for any that are relevant.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| description | No | What this node is about | |
| domain | Yes | The domain or project this belongs to (e.g. 'deep-game', 'sedex', 'general') | |
| label | Yes | Short name for this node (e.g. 'RST $10 boot crash') | |
| occurred_at | No | Optional ISO8601 date or datetime when this event or decision actually happened (e.g. '2026-04-01' or '2026-04-01T14:30:00Z'). Distinct from when it was filed. | |
| related_to | No | Optional list of nodes to auto-connect at creation time. Each item is either a plain node ID string (creates a connects_to edge) or an object with id and relationship fields. Invalid or unknown IDs are silently skipped. | |
| tags | No | Space-separated synonyms and keywords that improve search recall. Examples: 'testing gradle kotlin approval'. These are searched alongside label, description, and why_matters. Populate this with alternative terms an agent might use to find this node later. | |
| transient | No | Set to true for short-lived knowledge: ticket state, sprint notes, or anything expected to become stale within days. Transient nodes older than 7 days are surfaced by whats_stale as archiving candidates. | |
| why_matters | No | Why this is significant - the 'so what' |