{"version":"2.1.271","anchor":"permission-rule-and-hook-edits-now-wait-for-background-setti","canonical_anchor":"permission-rule-and-hook-edits-now-wait-for-background-setti","heading":"Permission-rule and hook edits now wait for background settings work before returning","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/permission-rule-and-hook-edits-now-wait-for-background-setti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Permission-rule and hook edits now wait for background settings work before returning\n\nPermission and hook edits now wait for background settings work to finish before confirming success\n\n**What**\n\nAfter Claude Code writes a permission rule (an allow or deny entry), removes one, or edits a hook, it now waits (up to 5 seconds) for a background settings-saving process to finish, via a new helper, before reporting the change as successful.\n\n**Why**\n\nThis reduces the chance of Claude Code reporting a permission or hook edit as done before it has actually finished being written to disk, avoiding a race where the change appears successful but hasn't fully saved yet.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}