{"version":"2.1.248","anchor":"memory-tool-errors-now-carry-stable-reason-codes","canonical_anchor":"memory-tool-errors-now-carry-stable-reason-codes","heading":"Memory tool errors now carry stable reason codes","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/memory-tool-errors-now-carry-stable-reason-codes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Memory tool errors now carry stable reason codes\n\nMemory write failures now carry fixed reason codes like store_full or content_secret.\n\n**What**\n\nFailures when writing to Claude's memory store map to fixed codes such as `store_full`, `content_too_large`, `content_secret` and `invalid_path`, so the cause is identifiable rather than a bare message.\n\n**Details**\n\n- One case detects credentials in the content and tells you to remove it, adding that if the credential is real you should rotate it.\n\n**Evidence**\n\n`memory content appears to contain a credential or API key; remove it before writing. If the credential is real, rotate it.`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}