{"version":"2.1.311","anchor":"working-sync-syncer-gains-an-fswatch-path-on-linux-with-an","canonical_anchor":"working-sync-syncer-gains-an-fswatch-path-on-linux-with-an","heading":"Working-folder sync on Linux listens for file changes instead of only polling","tier":"internal","area":"Performance","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/working-sync-syncer-gains-an-fswatch-path-on-linux-with-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Working-folder sync on Linux listens for file changes instead of only polling\n\nOn Linux, working-folder sync now listens for file change notifications and falls back to polling; `CLAUDE_CODE_DISABLE_WORKING_SYNC_WATCH` turns this off\n\n**What**\n\nClaude Code has a sync loop that keeps track of changes in your working folder. Before, it only checked at a fixed interval, which is called polling. On Linux it now also asks the system to send a notification whenever something in the folder changes.\n\nBefore relying on those notifications, Claude Code tests them. It makes a small permission change on the folder and waits to see the notification arrive. If no notification comes, an error occurs, or a change is missed, it goes back to polling. Once the notifications prove reliable, it still polls, but less often.\n\nThis happens only on Linux, and only when `CLAUDE_CODE_DISABLE_WORKING_SYNC_WATCH` is not set. Setting that environment variable keeps the old polling-only behaviour.\n\n**Why**\n\nFile syncing for remote sessions on Linux now reacts to changes as they happen instead of waiting for the next check. If it causes problems, `CLAUDE_CODE_DISABLE_WORKING_SYNC_WATCH` is the way to switch it off.\n\n- Area: Performance\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}