{"version":"2.1.224","anchor":"progress-and-failure-messages-for-cloud-file-seeding","canonical_anchor":"progress-and-failure-messages-for-cloud-file-seeding","heading":"Progress and failure messages for cloud file seeding","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/progress-and-failure-messages-for-cloud-file-seeding","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Progress and failure messages for cloud file seeding\n\nCloud file uploads show progress and a clear outcome, falling back to the git bundle on failure.\n\n**What**\n\nWhile a cloud session uploads the files it starts from, you see a progress line built from how many uploads have settled out of the total. On finish you get one of four outcomes: a summary, a timeout note, an unavailable note, or a could-not-finish note. Each of the failure cases ends by saying the session starts from the git bundle alone. This only appears on the container-sync file path behind `tengu_violin_wood`.\n\n**Evidence**\n\n`Cloud file sync is unavailable for this session; starting from the git bundle alone`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.224; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Names: `container_sync`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}