{"version":"2.1.290","anchor":"permission-denied-events-now-use-the-post-hook-result","canonical_anchor":"permission-denied-events-now-use-the-post-hook-result","heading":"Permission denials are reported based on the final decision","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/permission-denied-events-now-use-the-post-hook-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Permission denials are reported based on the final decision\n\nClaude Code now reports a permission denial to SDK programs based on the final decision, after any overrides\n\n**Unclear.** It is not clear which denials are left out of the report.\n\n**What**\n\nWhen Claude Code is not allowed to use a tool, it can send a message saying the permission was denied to programs that drive it through the SDK. That message is now based on the final decision, after hooks or other checks have had their say, rather than on the first decision. Some denials are not reported at all.\n\n**Why**\n\nIf a hook or automatic check overturns a decision, programs reading these messages now see the outcome that actually took effect.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}