{"version":"2.1.238","anchor":"files-over-the-per-turn-sync-allowance-are-now-deferred-not-","canonical_anchor":"files-over-the-per-turn-sync-allowance-are-now-deferred-not-","heading":"Files over the per-turn sync allowance are now deferred, not silently dropped","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/files-over-the-per-turn-sync-allowance-are-now-deferred-not-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Files over the per-turn sync allowance are now deferred, not silently dropped\n\nFiles over one turn's sync allowance are now deferred to later turns rather than just warned about.\n\n**What**\n\nWhen a cloud session changes more files than one turn's sync allowance covers, Claude Code prints an info line saying the rest will sync over the next turns, instead of only warning that you are over budget.\n\n**Details**\n\n- The admission calculation reports how many files were held back by the allowance, and the sync worker result carries an optional count of files skipped as deferred.\n- The new info line is separate from, and shown alongside, the existing over-budget warning.\n\n**Evidence**\n\n`Claude changed in the cloud session will sync here over its next turns`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}