{"version":"2.1.284","anchor":"permission-rule-and-hook-edits-are-refused-only-when-the-set","canonical_anchor":"permission-rule-and-hook-edits-are-refused-only-when-the-set","heading":"Settings files with only warnings no longer block rule and hook edits","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/permission-rule-and-hook-edits-are-refused-only-when-the-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Settings files with only warnings no longer block rule and hook edits\n\nRemoving a permission rule or editing a hook is now refused only when the settings file has real errors, not just warnings\n\n**Unclear.** Whether the hook-editing check is also changed in this release, or only the rule removal.\n\n**What**\n\nWhen Claude Code removes a permission rule or edits a hook (a command that runs automatically at certain points), it first checks the settings file. Before, the file counted as broken if it failed to load and was not empty, and the edit was refused with \"fix it by hand first\". The file is now read properly, and the edit is refused only if it has errors that are more serious than warnings.\n\n**Why**\n\nA settings file that has only warnings no longer stops you from changing rules or hooks through Claude Code.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}