Update a memory entry
Edit an entry’s content, description, or its key. The key is mutable.
content, refine its description, or re-key it.
The key is mutable
Thekey is not a fixed identity, it is a field you can change like any other:
key is how an agent loads the entry through get_memory and how the cascade resolves it. Change the key and any prompt or code that referenced the old one stops finding it. The entry keeps its mementry_... id across a re-key; only the lookup handle moves.
It merges
Send only what you are changing, and the rest survives. Acontent-only update leaves key and description intact, verified: patch only content and the entry keeps its key and description.
One consequence of the merge: setting an optional field like description to an empty string reads as “no change”, not “clear it”, so the old value stays. Send the value you want rather than relying on an empty string to blank a field.
Related
Create a memory entry
key, description, and content fields you edit here.Get a memory entry
content after an edit.Memory layers
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
Memory layer ID. Accepts canonical memlyr_… form or external_id: form.
"memlyr_01HXKD2E5NQM3T9AYWCFFFBMJH"
"mementry_01HXKD2E5NQM3T9AYWCF5E52Z0"
Body
UpdateResourceMetadata contains the user-provided fields for updating a workspace-scoped resource. Read-only fields (id, account_id, workspace_id, profile_id, created_at) are excluded since they are set by the server.
MemoryEntryUpdateSpec is the input shape for UpdateMemoryEntry. Fields present in the request's update_mask are applied; unset fields are left alone. The source oneof is optional for updates — omit it to leave the body untouched, or set exactly one branch to replace it.
Response
OK
MemoryEntryDetail is the full representation of an entry, including the resolved content body. Returned by GetMemoryEntry, CreateMemoryEntry, and UpdateMemoryEntry.
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
MemoryEntrySpec is the metadata portion of an entry — the fields that identify and describe it, without the body. It appears on both the summary (MemoryEntry) and detail (MemoryEntryDetail) views.
The resolved body of the entry. For entries created or updated via an upload_id, this is the ingested content, not the original upload handle. May be empty; an entry with only a key and description is valid (e.g., a stub skill being drafted, or an entry where the frontmatter alone is the payload).