You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MemoryArea: what it touches
ImprovementsKind: in v2.1.224,
ImprovementsSection of the release
What
Saving to a memory store that is read-only in the current session now fails immediately with the reason read_only and a list of the stores you can write to, instead of appearing to succeed and not persisting.
Details
The system prompt describing the memory index now names the store that owns each entry and marks read-only indexes.
Only reached when connected memory stores are in play; which flag enables those is not settled by anything in this build.
Evidence
is read-only in this session; changes will not persist.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.