You'll notice
Useful3 Signal2
Saving to a read-only memory store now fails immediately and lists stores you can write to.
What's wrong with this entry?
Anonymous. No account, no email.
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.