memory.write
Persist structured memory writes for checkpoints, implementation decisions, and compact recall artifacts. Use stable filenames to preserve continuity and deduplication.
Instructions
State-changing durable memory write used for checkpoints, implementation decisions, and compact recall artifacts. Parameter interactions: projectName should match the project used by memory.search; fileName is the logical lineage key (stable fileName preserves continuity and dedupe behavior); topicPath controls retrieval partitioning and, if omitted, is derived from fileName. content should be concise and factual (avoid full transcripts; preserve numeric facts verbatim). Side effects: successful writes may trigger asynchronous fanout/indexing/rollup work. ok=true with event_id means the write was accepted, but per-target fanout can still be pending/retrying and is returned in fanout/warnings. Do not use this for retrieval or diagnostics: use memory.search for reads and health for readiness checks. On auth/upstream errors this returns isError=true with structured error payload.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectName | Yes | Project identifier for the write (must match intended retrieval scope and future search project). | |
| fileName | Yes | Logical memory filename/path used for grouping and lookup (for example: notes/codex/xyz.md). Keep stable across updates to preserve continuity. | |
| content | Yes | Memory payload to persist. Keep numeric facts verbatim. Secret handling follows server policy (redact/block/allow). | |
| topicPath | No | Optional topic hierarchy for retrieval scoping (for example: runbooks/runtime-hardening). If omitted, topic is derived from fileName. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | No | ||
| event_id | No | ||
| warnings | No | ||
| fanout | No | ||
| deduped | No | ||
| latest_hash_unchanged | No |