Update a memory changedapi/beta/memory_stores/memories/update
Nearest release: v2.1.283, published 3 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+3added
Lines−3removed
From line
159
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits10to this page, all time
The whole hunk
from line 159, old and new numbered
/
from line 159
159159
160160- `precondition: optional BetaManagedAgentsPrecondition`
161161
162 Optimistic-concurrency precondition: the update applies only if the memory's stored `content_sha256` equals the supplied value. On mismatch, the request returns `memory_precondition_failed_error` (HTTP 409); re-read the memory and retry against the fresh state. If the precondition fails but the stored state already exactly matches the requested `content` and `path`, the server returns 200 instead of 409.
162 Optional optimistic-concurrency precondition. When supplied, the update applies only if the memory's current state matches; on mismatch the request returns `memory_precondition_failed_error` (HTTP 409). When omitted, the update is unconditional.
163163
164164 - `type: "content_sha256"`
165165
from line 191
191191
192192 - `created_at: string`
193193
194 A timestamp in RFC 3339 format
194 When this memory was created, in RFC 3339 format.
195195
196196 format: date-time
197197
from line 209
209209
210210 - `updated_at: string`
211211
212 A timestamp in RFC 3339 format
212 When this memory was last modified, in RFC 3339 format. Use this as a cheap freshness signal; for who made the change, look up the head version's `created_by` via [List memory versions](/docs/en/api/beta/memory_stores/memory_versions/list).
213213
214214 format: date-time
215215
No line in this hunk matches that.