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 sync no longer limits root-only folders to top-level files

The rootOnly mode is removed: nested files are no longer skipped and the "files stay in the cloud" warning is gone

Group of 3 You'll notice Bug Fixes
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File ReadingArea: what it touches
Bug FixesKind: in v2.1.283,
Bug FixesSection of the release

What

When a cloud session edits files, Claude Code syncs them back to a folder on your machine. Some folder setups used a restricted rootOnly mode that only handled files directly in the folder, not in subfolders. That restriction is removed:

  • The file reading step no longer skips any path inside a subfolder as "unreadable" for root-only sources.
  • The by-name backend no longer has a rootOnly mode. Before, nested paths in that mode failed and the sync round was skipped as anchor_degraded, with the warning "Files Claude changed in the cloud were not placed on this machine and stay in the cloud session". That warning is gone.
  • The directory operation that always reported unavailable for root-only backends now tries to run for them. Only the by_name backend still reports unavailable.

Why

Files in subfolders that were previously skipped may now be read and placed on your machine. The case where cloud edits quietly stayed in the cloud now either works or fails in some other way.

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 doubtWhich Claude Code feature uses root-only sources is not established.

See this entry in the whole of v2.1.283 →

Feedback