{"version":"2.1.319","anchor":"settings-watcher-compares-file-content-against-its-own-write","canonical_anchor":"settings-watcher-compares-file-content-against-its-own-write","heading":"Edits to a settings file right after Claude Code writes it are no longer missed","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/settings-watcher-compares-file-content-against-its-own-write","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Edits to a settings file right after Claude Code writes it are no longer missed\n\nClaude Code now ignores a settings file change only if the file still holds what it wrote, so a quick edit by someone else is picked up\n\n**What**\n\nClaude Code watches its settings files for changes. When it writes one itself, it ignores the change it caused. Before, it ignored any change within a short time after its own write. Now it ignores the change only if the file still holds exactly what Claude Code wrote. If the content differs, or the file cannot be read, the change is treated as coming from somewhere else and is loaded.\n\n**Why**\n\nAn edit you or another program make just after Claude Code saves a settings file is no longer silently ignored.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}