{"version":"2.1.224","anchor":"untracked-files-can-be-seeded-into-a-cloud-session","canonical_anchor":"untracked-files-can-be-seeded-into-a-cloud-session","heading":"Untracked files can be seeded into a cloud session","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/untracked-files-can-be-seeded-into-a-cloud-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Untracked files can be seeded into a cloud session\n\nTeleporting to a cloud session can upload your untracked files so the remote starts with them.\n\n**What**\n\nTeleporting to a cloud session can now inventory your git root and upload untracked working-tree files so the remote session starts with them, reporting progress as it goes. It needs both the `tengu_violin_wood` gate, whose fallback is off, and the per-project setting `remoteFileMode` set to `container_sync`. If the upload times out or is unavailable, teleport falls back to sending the git bundle alone.\n\n**Details**\n\n- Uploaded files go under a `.ccr-seed` prefix accompanied by `manifest.json` and `ready.json`.\n- New telemetry events: `tengu_dir_sync_inventory` and `ccr_dir_sync_seed`.\n\n**Evidence**\n\n`Cloud file sync timed out after `\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: `remoteFileMode`, `container_sync`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}