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 ·

Directory sync refuses to place files on machines that cannot anchor folders

Directory sync now gives up instead of placing files by name when folder anchoring is unavailable, unless CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING is set

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
2Signal: worth watching, 1 to 5
Cloud SyncArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release
What

Directory sync is Claude Code's syncing of a folder with a cloud session. Anchoring is how it keeps a fixed hold on a folder while placing files, rather than going by the folder's name each time. On some machines anchoring cannot be used. Examples are a missing native interface, a missing Linux process filesystem, an unstable folder identity, or a platform that is not supported.

On those machines, directory sync used to fall back to placing files by name, limited to the root folder. It now reports anchoring as unavailable and gives up instead.

Placing files by name now happens only when you set CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING, and in that mode it is no longer limited to the root folder. The related error message now names that variable.

Why

Placing files by name is less safe than anchoring, so refusing is the safer default. The cost is that on machines without anchoring support, files from the cloud may not be downloaded.

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 what, if anything, is shown to you when sync gives up because anchoring is unavailable.

See this entry in the whole of v2.1.283 →

Feedback