{"version":"2.1.283","anchor":"file-sync-sizing-history-walk-for-created-empty-starts-and","canonical_anchor":"file-sync-sizing-history-walk-for-created-empty-starts-and","heading":"File sync sizing now handles repositories that started empty","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/file-sync-sizing-history-walk-for-created-empty-starts-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### File sync sizing now handles repositories that started empty\n\nBefore offering file sync, Claude Code can now measure git history size for repositories that started empty, and checks untracked size first\n\n**Unclear.** It is not clear when the \"created_empty\" starting point is used or what the first-upload limit is.\n\n**What**\n\nBefore Claude Code offers file sync for a checkout, it measures the checkout to see whether it is small enough to sync. That measurement now handles a starting point called \"created_empty\". In that case, Claude Code measures how many bytes the git history takes up and compares that with a limit on the first upload. History that git has repacked, meaning compressed and reorganised, is counted at 1.2 times its size.\n\nOther changes:\n\n- The measurement accepts new options: `monorepo`, `firstUploadMaxBytes` and `historyWalkBudgetMs`.\n\n- The check for untracked files being too large now runs before the check for tracked files being too large. Untracked files are files git is not recording.\n\nWhen a checkout does not qualify, Claude Code shows a message starting \"File sync is not offered for this checkout:\".\n\n**Why**\n\nThis changes which repositories are offered file sync in cloud sessions. Because untracked files are now checked first, a checkout that is too large in both ways may be refused for its untracked files.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}