{"version":"2.1.292","anchor":"memory-extraction-skipped-when-a-permission-rule-would-refus","canonical_anchor":"memory-extraction-skipped-when-a-permission-rule-would-refus","heading":"Background memory saving is skipped when your permission rules block memory writes","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/memory-extraction-skipped-when-a-permission-rule-would-refus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Background memory saving is skipped when your permission rules block memory writes\n\nClaude Code skips its background memory runs when a permission rule would refuse writes to the memory folder, and can warn you\n\n**What**\n\nClaude Code can save useful facts from a conversation into a memory folder in the background, and can also tidy those memories up in a separate background run. Permission rules are settings that allow or refuse what Claude Code may do, such as writing to certain folders.\n\nBoth background runs now check your permission rules first. If a rule would refuse writes to the memory folder, the run is skipped:\n\n- Saving new memories from the conversation is skipped.\n\n- The background run that consolidates existing memories is skipped.\n\nIn either case Claude Code records why it skipped and may show you a warning.\n\n**Why**\n\nBefore this change these runs started even when your rules meant they could never write anything. Now they do not waste effort on work that cannot succeed, and the warning tells you that your own rule is the reason memories are not being saved.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}