{"version":"2.1.302","anchor":"settings-watch-failure-now-reported-with-a-named-reason","canonical_anchor":"settings-watch-failure-now-reported-with-a-named-reason","heading":"Settings watcher failures are logged with a named reason","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/settings-watch-failure-now-reported-with-a-named-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Settings watcher failures are logged with a named reason\n\nWhen Claude Code fails to start watching your settings for changes, the error is now logged under a named reason\n\n**What**\n\nClaude Code watches your settings files so it notices when they change. When that watcher fails to start, the error is now logged under a named reason, settingsWatchNotArmed, instead of as a plain log line.\n\n**Why**\n\nThis only changes what is recorded for diagnosing problems; what Claude Code does is the same.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}