Update a memory store
Update a memory store through the OMA API.
?beta=true.Authorizations
OMA workspace API key.
Path Parameters
Path parameter memory_store_id
Query Parameters
Selects the beta API contract for this endpoint. Must be true.
true Body
New human-readable name for the store. 1–255 characters; no control characters. Renaming changes the slug used for the store's mount_path in sessions created after the update.
1 - 255New description for the store, up to 1024 characters. Pass an empty string to clear it.
1024Metadata patch. Set a key to a string to upsert it, or to null to delete it. Omit the field to preserve. The stored bag is limited to 16 keys (up to 64 chars each) with values up to 512 chars.
Response
Successful response (OK)
Response from updating a memory_store. Returns the store with the changes applied.
memory_store Unique identifier for the memory store (a memstore_... tagged ID). Use this when attaching the store to a session, or in the {memory_store_id} path parameter of subsequent calls.
Human-readable name for the store. 1–255 characters. The store's mount-path slug under /mnt/memory/ is derived from this name.
Timestamp when the store was created.
Timestamp when the store's name, description, or metadata was last modified. Memory writes inside the store do not advance this.
Free-text description of what the store contains, up to 1024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent. Empty string when unset.
Arbitrary key-value tags for your own bookkeeping (such as the end user a store belongs to). Up to 16 pairs; keys 1–64 characters; values up to 512 characters. Returned on retrieve/list but not filterable.
Timestamp when the store was archived, or null if active. Set once and never cleared; archiving is one-way. Archived stores are read-only and cannot be attached to new sessions.