Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Cloud directory sync tracks git repository identity more precisely

Directory sync now records each downloaded apply's written files and upload generation, and compares the shared .git directory's identity

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

What

Cloud directory sync keeps a journal of what it has copied between your machine and a cloud session, and it records which git repository a folder belongs to. A git worktree is an extra working folder that shares one repository. The shared .git directory behind them is called the common dir.

  • Journal entries in downApplied, which record files applied from the cloud to your machine, now include wrote (the paths written or removed) and after (the upload generation at that time).
  • An entry is now matched on both its turn and its generation, not the turn alone.
  • The recorded git information in servedLinked gains commonDirId and commonDirBorn.
  • When checking whether two recorded git locations are the same repository, Claude Code now also compares commonDirId and its creation time if they were recorded, not only the common dir's path.
  • As a result, replacing the shared .git directory at the same path now counts as a different repository.

Why

Sync can now tell apart repeated applies of the same turn across different uploads, and it no longer treats a repository that was deleted and recreated at the same path as the same one.

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 stated which visible Claude Code feature depends on this comparison.

See this entry in the whole of v2.1.284 →

Feedback