{"version":"2.1.288","anchor":"config-settings-reapply-path-removed","canonical_anchor":"config-settings-reapply-path-removed","heading":"The path for reapplying settings changes after a ConfigChange hook was removed","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/config-settings-reapply-path-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### The path for reapplying settings changes after a ConfigChange hook was removed\n\nClaude Code no longer has its separate step that ran ConfigChange hooks and then reloaded a changed settings file\n\n**Unclear.** It is not clear whether another path now does this reapplying.\n\n**What**\n\nClaude Code had a separate step for reapplying a changed settings file. It first ran your `ConfigChange` hooks, and if none of them blocked it, it reloaded the settings. A hook is a command you set up for Claude Code to run automatically at certain moments, and `ConfigChange` hooks run when a configuration file changes during a session. That reapply step has been removed. So has the message saying a `ConfigChange` hook blocked reapplying.\n\n**Why**\n\nIf you use `ConfigChange` hooks to vet settings reloads, they may no longer be asked before a changed settings file is reapplied this way.\n\n- Area: Hooks\n- Names: `ConfigChange`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}