A memory store is a persistent mounted resource with a path-based file tree. Mount it at session creation; the agent reads and writes it with file tools, and its content persists across sessions.
Memory model
Memory stores use a three-layer model:
- Memory Store: a logical container with a name and description. A workspace can contain multiple memory stores.
- Memory: a single file inside a memory store, consisting of a path and a UTF-8 text body, such as a Markdown note. Every create, modify, and delete automatically produces a historical version.
- Version: a historical snapshot of a memory. Versions can be listed and viewed, and the body of a specific version can be redacted.
resources when creating a session, with read-only (retrieve only) or read-write (write back to the store) access. The mount path is generated by the server from the store name, in the form /mnt/memory/<name>. A memory store can only be mounted at session creation; after creation, mounts cannot be added, removed, or changed. To make adjustments, create a new session.
Store operations
Operation | Endpoint | Description |
|---|---|---|
| Creates a memory store; returns an ID with the | |
| Lists stores paginated in reverse creation order; archived stores excluded by default | |
| Retrieves store metadata | |
| Updates the name, description, and metadata | |
| Irreversible; the store can no longer be written or bound to new sessions, and existing mounts become read-only |
Memory operations
Write operations require the memory store to be unarchived.
Operation | Endpoint | Description |
|---|---|---|
| Creates a memory file; returns an ID with the | |
| Sorted by path with prefix filtering; keyword search over bodies is not supported | |
| Reads the body; an archived but undeleted store can still be read | |
| Modifies the body, renames, or updates atomically; supports the | |
| Deletes the current file; historical versions are kept |
Version operations
Version queries do not require the current memory to still exist.
Operation | Endpoint | Description |
|---|---|---|
| Reverse chronological order; filterable by memory, operation type, and time range | |
| Reads a specific historical version for reviewing old content; does not roll back the current memory | |
| Erases the body of the specified version; irreversible and does not affect the current memory |