{"version":"2.1.224","anchor":"read-only-memory-stores-are-refused-up-front","canonical_anchor":"read-only-memory-stores-are-refused-up-front","heading":"Read-only memory stores are refused up front","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/read-only-memory-stores-are-refused-up-front","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Read-only memory stores are refused up front\n\nSaving to a read-only memory store now fails immediately and lists stores you can write to.\n\n**What**\n\nSaving 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.\n\n**Details**\n\n- The system prompt describing the memory index now names the store that owns each entry and marks read-only indexes.\n- Only reached when connected memory stores are in play; which flag enables those is not settled by anything in this build.\n\n**Evidence**\n\n`is read-only in this session; changes will not persist.`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}