{"version":"2.1.305","anchor":"permission-persistence-from-hooks-no-longer-rebuilds-the-per","canonical_anchor":"permission-persistence-from-hooks-no-longer-rebuilds-the-per","heading":"Permissions saved by hooks are applied without rebuilding permission settings","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/permission-persistence-from-hooks-no-longer-rebuilds-the-per","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Permissions saved by hooks are applied without rebuilding permission settings\n\nWhen a hook saves a permission, Claude Code now applies the update directly instead of first rebuilding its permission settings\n\n**Unclear.** Whether this changes which permissions are saved, or only how they are passed along, is not settled.\n\n**What**\n\nA hook is a script you set up to run when something happens in Claude Code. A hook can approve a permission and ask for it to be saved. Claude Code now hands those permission updates straight to its state instead of first rebuilding the full set of permission settings around them.\n\n**Why**\n\nThis may change how permissions approved by hooks are applied.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}