Update a memory layer
Rename a layer, or change its TTL. The type is fixed, and system-managed layers are off limits.
System-managed layers are read-only
An episodic layer that Cadenya created for an agent hassystemManaged: true. Every write to it is a 403, whether you target the name, the type, or its entries:
store_memory. You read it in the cascade; you do not edit it.
The type is fixed
You cannot change a layer fromSKILLS to EPISODIC or back. The update writes name, description, and TTL, and never touches the type.
The TTL follows the merge rules
expiresAt behaves like every other field on a PATCH: the update merges, so a field you leave out is kept, and a zero value needs updateMask to land.
updateMask and send no value. Omitting it alone leaves it in place, because a merge cannot tell “clear this” from “did not mention it”:
SKILLS layer sets when its entries stop resolving. get_memory and search_memory both filter on expiry, so an expired layer’s entries read as absent even while the layer row remains.
Related
Create a memory layer
Update a variation
updateMask rule for zero values.List memory layers
systemManaged, which decides whether you can edit at all.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"
Body
Response
OK
MemoryLayer is a named container of memory entries that can be composed into an objective's memory cascade. Layers are workspace-scoped resources. The layer type controls how its entries participate in the agent loop — see MemoryLayerType for details.
See "Memory cascade composition" above for how layers compose at lookup time.