{"version":"2.1.292","anchor":"auto-memory-tool-denials-log-a-reason","canonical_anchor":"auto-memory-tool-denials-log-a-reason","heading":"Blocked tools during auto memory now log a reason","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/auto-memory-tool-denials-log-a-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Blocked tools during auto memory now log a reason\n\nWhen a tool is blocked during auto memory, the debug log and usage data now say why\n\n**What**\n\nWhen Claude Code blocks a tool while working on its auto memory, the line it writes to the debug log now includes the reason. The usage data it records about the block also gains the reason, where before it held only the tool's name.\n\n**Why**\n\nThis only adds detail to records. If you read the debug log, you can now see why a tool was blocked.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}