Available on crate feature
managed-agents-preview only.Expand description
Memory stores: persistent text documents that survive across sessions.
A memory store is a workspace-scoped collection of small text files
(memories) addressed by path. Sessions mount stores under
/mnt/memory/ and read/write them with the standard agent toolset.
Every mutation creates an immutable MemoryVersion for audit and
point-in-time recovery.
Limits: max 8 stores per session, individual memories capped at 100KB (~25K tokens). Structure as many small focused files.
Structs§
- Create
Memory Request - Request body for
POST /v1/memory_stores/{id}/memories. - Create
Memory Store Request - Request body for
POST /v1/memory_stores. - List
Memories Params - Optional knobs for
Memories::list. - List
Memory Stores Params - Optional knobs for
MemoryStores::list. - List
Memory Versions Params - Optional knobs for
MemoryVersions::list. - Memories
- Namespace handle for memory operations on a single store.
- Memory
- One memory inside a store.
- Memory
Store - A workspace-scoped collection of memories.
- Memory
Stores - Namespace handle for the memory-stores API.
- Memory
Version - An immutable historical version of a memory.
- Memory
Versions - Namespace handle for memory-version (history) operations on a store.
- Update
Memory Request - Request body for
POST /v1/memory_stores/{id}/memories/{mem}(update). - Update
Memory Store Request - Request body for
POST /v1/memory_stores/{id}(update).
Enums§
- Memory
Actor - Who or what produced a
MemoryVersion. Tagged-union of session, API, or user actor. - Memory
Precondition - Optimistic-concurrency precondition for
UpdateMemoryRequest. - Memory
Version Operation - What mutation produced a
MemoryVersion. Closed enum.