{"version":"2.1.295","anchor":"permission-hook-decision-allow-no-longer-short-circuits","canonical_anchor":"permission-hook-decision-allow-no-longer-short-circuits","heading":"An allow decision in one permission path no longer ends the check early","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/permission-hook-decision-allow-no-longer-short-circuits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### An allow decision in one permission path no longer ends the check early\n\nIn one permission check, an allow decision now goes on to later handling instead of being returned at once\n\n**Unclear.** Which permission path this is, and so which tool calls it affects, is not known.\n\n**What**\n\nIn one of the steps where Claude Code decides whether a tool may run, an earlier decision used to be returned straight away whenever there was one. Now it is returned straight away only when it is something other than allow. An allow decision goes on to the handling that follows.\n\n**Why**\n\nThis could change when tools that were allowed automatically still pass through the normal permission steps.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}