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

Cloud file-sync snapshot reads committed .gitattributes from more sources

Cloud file sync now reads committed .gitattributes from extra commits or trees and reports more reasons a sync was not applied

Entry
JSON All of v2.1.281
EntryKind: in v2.1.281,
ChangesSection of the release
What

This concerns syncing files between your machine and a cloud session. .gitattributes is a git file that sets rules for particular paths. The sync snapshot changes as follows:

  • It can take extra attributeSources, each a commit or a tree (a saved folder state in git), and caches those attribute trees in its sync repository.
  • It reports attributesTrees and attributesNotKept, with the reason given as gone, overflow or missing.
  • It has several new error messages, such as "could not read back what the cloud session was last sent for the files kept on this machine".
  • Paths held at the state last sent to the cloud are now also protected when files or directories are moved.
  • Sync results can report two new reasons for not being installed: "deferred" and "stale_basis".
  • Installs from your machine are folded into the tree both sides agree on.
Why

The cloud side can respect more of your committed .gitattributes rules. When a sync is not applied, or something could not be read back, the report now says more precisely why.

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 doubtThe finding does not say what folding your machine's installs into the agreed tree changes for a user.

See this entry in the whole of v2.1.281 →

Feedback