Directory sync copies your working folder to another place, for example a cloud session. When it takes a snapshot, it now keeps the committed .gitattributes files it read inside its own sync repository. .gitattributes files tell git to transform some files, for example by changing line endings. If those kept files cannot be listed or stored, the snapshot is refused.
There are also new messages for git settings that sync cannot follow. Each message says how to fix the problem. The settings are:
- an attributes file set in git config
- an attribute tree
ignoreCaseset in an included config file- an attribute source set through environment variables
- a config location given as a relative path
When a snapshot is refused for one of these reasons, the cause is reported as an attribute source problem.
This stops files that git would transform from being uploaded exactly as they sit on disk. That could otherwise make the synced copy differ from what git would produce. In v2.1.282 the related remote switch was off by default; the flag server has since returned on for this site's account.
tengu_violin_soundpost Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.283: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.283. It isn't a statement about your account. What a flag value here can and cannot tell you
The link between this behaviour and the remote switch is indirect, so it is not certain that switch controls it.