Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Cloud file sync now refuses unsafe project roots and explains every skip

Cloud file sync refuses to run from your home or root directory and explains every skip.

You'll notice New Features
JSON All of v2.1.242
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Directory SyncArea: what it touches
New FeaturesKind: in v2.1.242,
New FeaturesSection of the release
What

Sync will not run at all when the checkout root is your home directory or above it, the filesystem root, or a directory that holds Claude Code's own configuration folder, and it declines hidden or system directories under home. When it does run, the messages now name the files and say why each one was skipped.

Details
  • Three outright refusal reasons for dangerous roots, plus two more for hidden and system directories under home (recorded as folder_hidden_under_home and folder_system_under_home).
  • New per-file explanations: nested git repositories are never entered, files inside dependency and build folders are skipped, uploads that are too slow are kept local and retried, and slow uploads that eventually landed are reported.
  • Deletions can now be held back or withheld as a group rather than silently applied.
  • The over-budget message now states the cap on new files per message.
  • These refusals are unconditional once sync is considered; the notifier text grew from about 9 lines to 17.
Evidence

File sync is off here: this checkout's git root holds, or sits inside, Claude Code's own configuration folder

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →

Feedback