{"version":"2.1.317","anchor":"settings-watcher-checks-for-edits-made-before-the-watch-went","canonical_anchor":"settings-watcher-checks-for-edits-made-before-the-watch-went","heading":"Settings edits made while Claude Code is starting are no longer missed","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/settings-watcher-checks-for-edits-made-before-the-watch-went","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Settings edits made while Claude Code is starting are no longer missed\n\nClaude Code now rechecks each settings file once its watch starts and reloads any file that changed after it was first read\n\n**What**\n\nClaude Code watches its settings files so it can pick up your edits without a restart. There was a short gap between reading the files at startup and the watch going live, and an edit made in that gap could be missed.\n\nNow, once the watch is running, Claude Code compares each settings file once against the version it read at startup. If the file changed in between, Claude Code reloads it and writes \"changed before its watch was live\" to its debug log. If the watch later reports that same version again, Claude Code ignores it, because it has already handled it.\n\n**Why**\n\nAn edit to your settings made while Claude Code was starting up could before be silently never applied. That gap is now closed.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}