{"version":"2.1.274","anchor":"new-memory-store-rejection-reasons-content-screened-and-ind","canonical_anchor":"new-memory-store-rejection-reasons-content-screened-and-ind","heading":"New memory-store rejection reasons: content_screened and index_too_large","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-memory-store-rejection-reasons-content-screened-and-ind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New memory-store rejection reasons: content_screened and index_too_large\n\nClaude Code now explains two new reasons memory writes can be rejected: content screening and an oversized index file\n\n**What**\n\nWhen Claude Code tries to save something to its memory store and the server rejects it, two new rejection reasons now come with user-facing explanations:\n\n- `content_screened`: the write failed a safety screening, without specifying which part of the content triggered it\n\n- A size-cap rejection for the memory index file (`MEMORY.md`), which has a much smaller size limit than the cap applied to individual memory files\n\n**Why**\n\nThis gives clearer feedback when a memory write fails, so you know whether it was blocked for safety reasons or because the index file grew past its (smaller) limit, rather than seeing an unexplained failure.\n\n- Area: Memory\n- Names: `content_screened`, `index_too_large`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}