{"version":"2.1.242","anchor":"file-sync-status-for-a-cloud-session-comes-with-a-stated-rea","canonical_anchor":"file-sync-status-for-a-cloud-session-comes-with-a-stated-rea","heading":"File-sync status for a cloud session comes with a stated reason","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/file-sync-status-for-a-cloud-session-comes-with-a-stated-rea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### File-sync status for a cloud session comes with a stated reason\n\nCloud file-sync status now states why sync is off instead of just showing off.\n\n**What**\n\nThe session snapshot sent to the host now includes a `directory_sync` block, and each off-state carries a written explanation: this directory was never set up for sync, the lookup failed, or sync was set up from a different directory on the same machine.\n\n**Details**\n\n- Without a sync handle for the session, the state reports as `not_opted_in`.\n- A `tengu_remote_headless_laptop_linked` event records the sync state, the reason, the file mode and whether a sync handle exists.\n\n**Evidence**\n\n`File sync for this session was set up from another directory on this machine: edits here are not uploaded, and Claude's changes are not written here.`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}