{"version":"2.1.296","anchor":"permission-request-hook-allow-path-now-checks-for-lost-permi","canonical_anchor":"permission-request-hook-allow-path-now-checks-for-lost-permi","heading":"A permission hook's allow no longer goes through if stricter rules were lost","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/permission-request-hook-allow-path-now-checks-for-lost-permi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### A permission hook's allow no longer goes through if stricter rules were lost\n\nWhen a `PermissionRequest` hook allows with permission updates, Claude Code withholds the allow if any stricter rule was lost\n\n**Unclear.** It is not stated what Claude Code does instead of allowing, such as asking or denying.\n\n**What**\n\nA `PermissionRequest` hook is a command that runs when a tool call needs a permission decision. It can answer allow and also send `updatedPermissions`, which are changes to your permission rules. Claude Code now counts whether any of those changes that would have made permissions stricter were lost. If any were, it does not allow the tool call. Before, it allowed as soon as the updates were applied.\n\nPermission updates are also skipped in one more mode.\n\n**Why**\n\nA hook's allow can no longer get past a restriction that was meant to apply.\n\n- Area: Permissions\n- Names: `updatedPermissions`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}