{"version":"2.1.280","anchor":"new-directory-sync-lag-notice-for-cloudremote-git-environme","canonical_anchor":"new-directory-sync-lag-notice-for-cloudremote-git-environme","heading":"New directory-sync-lag notice for cloud\/remote git environments","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-directory-sync-lag-notice-for-cloudremote-git-environme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New directory-sync-lag notice for cloud\/remote git environments\n\nCloud and remote sessions now get a warning when their git working directory hasn't caught up with your latest local upload\n\n**What**\n\nWhen you're working in a cloud or remote session, Claude Code keeps that session's git working directory (the folder holding your checked-out files) synced with the changes you upload from your local machine. If that sync falls behind, a new notice now appears telling you the current turn is running against stale files, since your newer local changes haven't arrived yet. Claude Code keeps retrying the upload on every turn until it succeeds.\n\n**Why**\n\nWithout this notice, a lagging sync would be invisible, and Claude Code could act on outdated files without you realizing it. Now you know when a response may not reflect your latest local edits.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}