{"version":"2.1.290","anchor":"settings-file-watcher-handles-project-scoped-dirs-and-unlink","canonical_anchor":"settings-file-watcher-handles-project-scoped-dirs-and-unlink","heading":"Settings reloads on Linux and WSL now check for real file changes","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/settings-file-watcher-handles-project-scoped-dirs-and-unlink","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Settings reloads on Linux and WSL now check for real file changes\n\nOn Linux and WSL, Claude Code now checks a settings file has really changed before reloading it, and notices when a watched folder is removed\n\n**Unclear.** Exactly what the new project-scoped tracking and file-detail check are for is not clear.\n\n**What**\n\nClaude Code watches its settings files so it can pick up edits without a restart. This watching has changed in three ways:\n\n- Settings files that belong to a specific project are now tracked.\n\n- On Linux or WSL (Windows Subsystem for Linux), when the watcher reports a change inside a watched folder, Claude Code first checks the file's details to confirm it really changed.\n\n- Claude Code now reacts when a watched settings folder is deleted.\n\n**Why**\n\nThese checks are meant to cut down on settings being reloaded when nothing has actually changed, which affects how settings refresh on Linux.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}