{"version":"2.1.232","anchor":"file-sync-can-now-anchor-to-the-commit-a-cloud-session-start","canonical_anchor":"file-sync-can-now-anchor-to-the-commit-a-cloud-session-start","heading":"File sync can now anchor to the commit a cloud session started from","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/file-sync-can-now-anchor-to-the-commit-a-cloud-session-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### File sync can now anchor to the commit a cloud session started from\n\nFile sync can pin to the exact commit a cloud session started from, disabling itself if unreadable.\n\n**What**\n\nPer-turn file sync, which keeps your local checkout in step with a session, previously could only start from an uploaded bundle. It can now also start from a remote commit reference, pinning sync to that exact commit. If the checkout cannot read that commit, sync turns itself off for the session and says so.\n\n**Details**\n\n- The sync origin is now a tagged value with a `remote_ref` kind carrying the agreed tree and the remote commit; arming pins the treeish to that commit, or to nothing for bundle origins.\n- The inventory record stores which kind of origin was used, and the `tengu_dir_sync_inventory` telemetry event gained a matching `origin_kind` field. The bundle scope is recorded only for bundle origins.\n- Two new failure notices ship with it; this path is only reached when a session actually has a remote-commit origin.\n\n**Evidence**\n\n`File sync is off for this session: the commit the cloud session started from cannot be read in this checkout`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}