{"version":"2.1.323","anchor":"settings-writes-consult-configchange-hooks-before-overwritin","canonical_anchor":"settings-writes-consult-configchange-hooks-before-overwritin","heading":"Settings writes no longer bring back an edit a ConfigChange hook blocked","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/settings-writes-consult-configchange-hooks-before-overwritin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Settings writes no longer bring back an edit a ConfigChange hook blocked\n\nWhen a ConfigChange hook blocked or is still judging a settings edit, Claude Code now writes from its last settings, not the file on disk\n\n**What**\n\nWhen Claude Code saves a change to one of your settings files, it now first checks your `ConfigChange` hooks. A hook is a command you set up to run automatically, and `ConfigChange` hooks run when a configuration file changes during a session. If a hook blocked the latest edit to the file, or is still deciding about it, Claude Code starts its write from the settings it last read. Before, it always re-read the file on disk and merged its change into that.\n\n**Why**\n\nAn edit a hook blocked can no longer slip back in, or be silently overwritten, when Claude Code writes the file.\n\n- Area: Hooks\n- Names: `ConfigChange`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}