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 ·

File sync refuses to start when this machine cannot place files safely

Folder sync now stops with a clear refusal when this machine cannot place its files safely, instead of carrying on in a degraded way

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
What

File sync copies a folder between this machine and a cloud session. Before a sync starts, Claude Code opens an anchor, the fixed point it uses to place files. Before, a failure here was only logged as "tree anchor not opened". Now:

  • If the anchor is unavailable, starting a folder sync is refused with the message "this machine cannot place its files safely" and details of why.
  • If the anchor cannot be read at all, a separate "unreadable" message is given.
  • A sync already running saves its record and stops.
  • Two background checks return no result instead of failing, and one logs that there is no anchored backend here.
  • The upload step no longer hides errors from opening the anchor.
Why

On machines where the anchor cannot work, you now get a plain refusal instead of a sync that quietly runs in a reduced state.

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 clear which platforms or conditions make the anchor unavailable.

See this entry in the whole of v2.1.283 →

Feedback