Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Cloud-session sync gains withheld-file causes and a 'device already has that work' reason

Cloud-to-machine sync adds four withheld_* causes and a new reason saying your machine already has the work

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

What

When you work in a cloud session, its changes can be synced back to your machine. Claude Code explains when that does not happen, and this release adds new reasons:

  • Four new causes for files being held back: withheld_unlistable, withheld_list_unapplied, withheld_list_unsettled and withheld_versions_too_many. Like other, host_config, legacy_tree and attribute_source, they are excluded from one warning path.
  • A new device_has_work explanation, "your machine already has that work", replaces word_absent, which said "this machine no longer takes the session's uploads in order".
  • Snapshot records gain deviceSnapshotEqualled.

Why

When work from a cloud session is not brought back to your machine, the reason shown is more specific, and more cases of files being held back are recognised.

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 unclear what this change on the warning path means for what you see.

See this entry in the whole of v2.1.284 →

Feedback