{"version":"2.1.292","anchor":"background-memory-pass-permission-denials-now-carry-reason-c","canonical_anchor":"background-memory-pass-permission-denials-now-carry-reason-c","heading":"Background memory permission refusals now carry a reason code","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/background-memory-pass-permission-denials-now-carry-reason-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Background memory permission refusals now carry a reason code\n\nWhen the background memory pass in a remote session is refused permission, the refusal now includes a code saying why; the message is unchanged\n\n**What**\n\nIn remote sessions, Claude Code can run a background memory pass that saves information for later. When that pass is refused permission to do something, the refusal now carries a reason code:\n\n- `memory_paused`\n\n- `no_memory_server`\n\n- `permission_rule`\n\n- `tool_not_allowed`\n\nThe refusal messages themselves are the same as before.\n\n**Why**\n\nThe codes mostly serve usage reporting. Nothing changes in what you see.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}