{"version":"2.1.300","anchor":"permission-check-faults-now-deny-the-tool-call-outright","canonical_anchor":"permission-check-faults-now-deny-the-tool-call-outright","heading":"A fault during a permission check now denies the action","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/permission-check-faults-now-deny-the-tool-call-outright","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### A fault during a permission check now denies the action\n\nIf Claude Code hits an internal fault while checking permission for a tool, the action is now denied instead of carrying on\n\n**What**\n\nBefore Claude uses a tool (an action such as running a command or editing a file), Claude Code checks whether it is allowed. If Claude Code itself hits a fault during that check, the action is now denied. Before, it went on to the usual next step. The message names the tool and says the permission check failed because of a fault in Claude Code, so the call is denied. Nothing in this session can fix it, and a retry is denied the same way.\n\n**Why**\n\nA broken permission check now blocks the action instead of risking letting it through. If you see this message, retrying in the same session will not help.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}