{"version":"2.1.271","anchor":"settings-file-watcher-falls-back-to-polling-when-native-fs-e","canonical_anchor":"settings-file-watcher-falls-back-to-polling-when-native-fs-e","heading":"Settings file watcher falls back to polling when native fs events don't fire","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/settings-file-watcher-falls-back-to-polling-when-native-fs-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Settings file watcher falls back to polling when native fs events don't fire\n\nClaude Code now falls back to polling settings files when native file-watching doesn't work on your system\n\n**What**\n\nClaude Code's detector for settings-file changes now checks whether native filesystem watching actually delivers change events on your machine. If the check finds the watcher stays silent, or fails outright (for example due to `EMFILE`, `ENFILE`, or `ENOSPC` errors \u2014 signs the system has run out of file-watch resources), it switches to checking settings files and directories on a timer instead of relying on native watching, and logs a warning plus a telemetry event.\n\n**Why**\n\nOn some systems, native file-watching silently doesn't work, which would mean changes to settings files go unnoticed. This fallback makes sure settings changes are still picked up even when that happens.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}