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.282 ·

Cloud file sync refuses damaged git data and handles unusual file names

Directory sync now refuses snapshots with tampered or old-format git data by name and copes better with file names that are not valid UTF-8

You'll notice Improvements
JSON All of v2.1.282
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File SyncArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release
What

Directory sync keeps your local folder and a cloud session in step by taking snapshots of your project with git, the version control tool. Several things about building those snapshots have changed:

  • Git data that fails an integrity check is now refused as "tampered", instead of being reported as a general git error.
  • Malformed git trees (the records of folder contents) are refused with a new "legacy_tree" reason.
  • Each snapshot is read back and checked against what it should contain.
  • Staged file names that are not valid UTF-8 text are carried through.
  • If something is staged where a folder holding such a name stood, the snapshot is refused, and you are told to commit that change first and then send again.
  • The snapshot now carries a list of the changes found in your staged files and your working folder.
Why

Sync is harder to fool with damaged or forged git data, and it copes better with file names in unusual encodings.

See this entry in the whole of v2.1.282 →

Feedback