You'll notice
Useful3 Signal4
Org memory documents now show version tokens and report conflicts so concurrent edits get retried instead of clobbered.
What's wrong with this entry?
Anonymous. No account, no email.
What
Reading an org memory document now shows a version token next to the updated date, writes report the version they produced, and a concurrent edit produces a distinct conflict result telling the model to re-read the document and retry with the fresh token. Requires org memory to be enabled for the session.
Details
- The conflict message is "The memory store reported a concurrent change to this document."
- The conflict result also carries the conflicting path taken from the server response.
- The version token is appended to reads in the form
[version: ...].
Evidence
The memory store reported a concurrent change to this document.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.