Cloud file sync holds back changes when .git/info/attributes looks unsafe
Files Claude changed in a cloud session are not applied locally when .git/info/attributes can't be read normally or could switch off git-crypt or git-lfs
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
Unclear It is not clear which sync paths use this check, or whether it is switched on for everyone.
What
When Claude works in a cloud session, Claude Code can copy the files it changed back onto your machine. Your project's .git/info/attributes file is a git settings file that says how particular files are handled. Claude Code now skips copying the changed files for that round if this file:
cannot be read as a regular file
holds rules that could switch off content filters such as git-crypt or git-lfs, which change file contents as git stores and restores them
The changed files stay in the cloud session, and a warning explains how to fix the problem.
Why
Without this check, sync could write plain, unfiltered content over files that git-crypt or git-lfs is meant to handle.
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 which sync paths use this check, or whether it is switched on for everyone.