Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

File sync sizing now handles repositories that started empty

Before offering file sync, Claude Code can now measure git history size for repositories that started empty, and checks untracked size first

Under the hood Internal Changes
JSON All of v2.1.283
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SyncArea: what it touches
Internal ChangesKind: in v2.1.283,
Internal ChangesSection of the release
What

Before 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.

Other changes:

  • The measurement accepts new options: monorepo, firstUploadMaxBytes and historyWalkBudgetMs.
  • 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.

When a checkout does not qualify, Claude Code shows a message starting "File sync is not offered for this checkout:".

Why

This 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear when the "created_empty" starting point is used or what the first-upload limit is.

See this entry in the whole of v2.1.283 →

Feedback