Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

File sync stops with a clear reason when a git setting changes attribute rules

File sync and teleport now stop with a named attribute_source reason when a local git setting changes which attribute rules git applies

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

Unclear Whether the FILE_SYNC_STOPPED.md marker file is gone or has only moved is not known.

What

Git can be told to treat certain files specially through attribute rules, for example in a .gitattributes file. A setting on your machine can change which of those rules git applies. File sync, which keeps your local folder and a cloud copy in step, cannot follow that.

  • A new failure cause, attribute_source, is raised when the repository's attribute settings come from a source such as attributes_file.
  • The failure detail now explains that "a git setting on the user's machine can change which attribute rules git applies, in a way file sync cannot follow". The text used to point to FILE_SYNC_STOPPED.md instead.
  • Teleport, which carries a session over to another machine, reports attribute_source_unread when uploading its bundle hits this case.
  • A check that decides whether a sync is eligible now also excludes the attribute_source cause, alongside other, host_config and legacy_tree.

Why

Sync now stops and names the reason instead of carrying on and possibly applying the attribute rules wrongly. If you see this message, a git setting on your machine is the thing to look at.

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 doubtWhether the FILE_SYNC_STOPPED.md marker file is gone or has only moved is not known.

See this entry in the whole of v2.1.283 →

Feedback