{"version":"2.1.284","anchor":"dir-sync-withheld-file-causes-excluded-from-a-warning-path","canonical_anchor":"dir-sync-withheld-file-causes-excluded-from-a-warning-path","heading":"Cloud-session sync gains withheld-file causes and a 'device already has that work' reason","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/dir-sync-withheld-file-causes-excluded-from-a-warning-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud-session sync gains withheld-file causes and a 'device already has that work' reason\n\nCloud-to-machine sync adds four withheld_* causes and a new reason saying your machine already has the work\n\n**Unclear.** It is unclear what this change on the warning path means for what you see.\n\n**What**\n\nWhen 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:\n\n- 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.\n\n- 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\".\n\n- Snapshot records gain `deviceSnapshotEqualled`.\n\n**Why**\n\nWhen 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.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}