{"version":"2.1.251","anchor":"directory-sync-has-an-explicit-offline-end-state","canonical_anchor":"directory-sync-has-an-explicit-offline-end-state","heading":"Directory sync has an explicit offline end-state","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/directory-sync-has-an-explicit-offline-end-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Directory sync has an explicit offline end-state\n\nCloud directory sync ending because you went offline now asks you to acknowledge it.\n\n**What**\n\nThe git-based directory sync used by cloud sessions can now end specifically because it went offline, which puts up a dialog asking you to acknowledge before sync is reported as ended. Telemetry records whether you acknowledged or the dialog went unanswered.\n\n**Details**\n\n- Reached through an offline callback that only the terminal surface supplies; no remote-config flag controls it.\n\n**Evidence**\n\n`tengu_dir_sync_git_offline_continued`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}