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.283 ·

Cloud sessions move conflicting files aside before bringing in your files

When your files arrive in a cloud session, files already at the same paths are moved to .git/claude-trash instead of being overwritten

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

Directory sync copies the files from your machine into a cloud session (a Claude Code session running on Anthropic's servers). When the cloud session starts from your uploaded files, files already in its folder at the paths your files need, such as files Claude created there, used to be overwritten directly. Now they are first moved into a trash folder, .git/claude-trash, inside the checkout. Files whose contents already match yours are left alone, and Claude is told when files have been moved.

If a later step of the checkout fails, the moved files are put back, and the failure message names anything that could not be restored. Two new failures switch sync off and explain why:

  • The trash folder could not be created
  • Files could not be moved aside

The notice shown while an upload is in progress now says your machine began uploading newer changes, rather than the starting files.

Why

Files that were already in the cloud folder are no longer silently overwritten when your own files arrive.

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 doubtExactly when this set-aside step runs, and whether directory sync is available to everyone, was not established.

See this entry in the whole of v2.1.283 →

Feedback