{"version":"2.1.271","anchor":"options-watch-auto-reload-on-hook-config-changes-reworkedad","canonical_anchor":"options-watch-auto-reload-on-hook-config-changes-reworkedad","heading":"Options-watch auto-reload on hook config changes reworked\/added","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/options-watch-auto-reload-on-hook-config-changes-reworkedad","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Options-watch auto-reload on hook config changes reworked\/added\n\nHook configuration changes now auto-trigger a reload with per-module logging\n\n**What**\n\nClaude Code now watches for a specific set of configuration-change events and, when one of those matching changes occurs, automatically reloads hooks modules. Each module's reload outcome \u2014 success, refusal, or failure \u2014 is logged with an \"options changed\" message.\n\n**Why**\n\nThis means changes to hook configuration can take effect automatically without requiring a manual restart, while still giving visibility into which modules reloaded cleanly and which didn't.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}