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 ·

Dir-sync: many new model notices when the user and cloud histories diverge

After directory sync in cloud sessions, Claude now gets notices for more cases where your history and the cloud's differ

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

In cloud sessions, Claude Code keeps the folder on your machine and the copy in the cloud in step, which is called directory sync. After a sync, Claude receives short notices about anything unusual. These notices now cover new cases:

  • Rewound commits whose files no longer match are named, and Claude is told to check git diff HEAD -- PATH.
  • Commits already on a remote are no longer re-created on top of your current commit, and Claude is told not to cherry-pick them (copy them over one by one).
  • When a file of yours sits where Claude had a directory, Claude's files are moved to the session trash.
  • Files not yet written because they were based on an out-of-date copy are listed with the note "sync settles this by itself".
  • A new notice covers the case where your machine cut a list short.
Why

When your history and the cloud copy disagree, Claude is now told what happened and what to do about it. It should avoid duplicating commits that are already on a remote and avoid acting on files that sync will fix by itself.

See this entry in the whole of v2.1.281 →

Feedback