{"version":"2.1.257","anchor":"cloud-directory-sync-now-reports-upload-failures-explicitly","canonical_anchor":"cloud-directory-sync-now-reports-upload-failures-explicitly","heading":"Cloud directory-sync now reports upload failures explicitly, not just size-cap holds","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/cloud-directory-sync-now-reports-upload-failures-explicitly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Cloud directory-sync now reports upload failures explicitly, not just size-cap holds\n\nClaude is now told outright when a turn's changes were not uploaded to your machine, not just when a size cap held them.\n\nThe cloud directory-sync status tracker gained a `notShipped` path that tells Claude, and records in a persisted report list, when this turn's changes were not uploaded to the user's local machine at all. This is distinct from the existing \"held back by size cap\" case, and later reports when uploads resume.\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}