{"version":"2.1.292","anchor":"memory-agent-permission-gate","canonical_anchor":"memory-agent-permission-gate","heading":"Permission rules now apply to the background memory saver","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/memory-agent-permission-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Permission rules now apply to the background memory saver\n\nThe background memory agent now follows your permission rules, may only write .md files in the memory folder, and says when saving is blocked\n\n**Unclear.** It is not settled whether this is new behaviour or existing behaviour that was moved, so it may not change anything for you.\n\n**What**\n\nClaude Code can save memories in the background using a separate agent (a helper that works on its own). That agent now has its own permission check:\n\n- It is refused MCP tools (tools from add-on servers) and anything that would need to ask you through a hook.\n\n- Your own permission rules are applied to it.\n\n- It may only read files, and write `.md` files inside the memory folder.\n\n- If your permission rules cannot be checked, it refuses rather than going ahead.\n\nWhen one of your rules blocks it, Claude Code shows a message that it is not saving memories.\n\n**Why**\n\nDeny and ask rules you have set can now stop memory saves, and you see a notice instead of saves failing silently.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}