{"version":"2.1.248","anchor":"cloud-session-creation-reports-whether-directory-sync-was-de","canonical_anchor":"cloud-session-creation-reports-whether-directory-sync-was-de","heading":"Cloud session creation reports whether directory sync was declared","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cloud-session-creation-reports-whether-directory-sync-was-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cloud session creation reports whether directory sync was declared\n\nCloud session creation records whether directory sync was declared to the server.\n\n**What**\n\nAfter a cloud session is created from a directory or folder seed, Claude Code now reports whether client-side directory sync was declared to the server, as one of not sent, accepted, or unbound. The sync itself additionally requires the git engine and a consent setting other than upload-only.\n\n**Details**\n\n- Seed paths gained a callback that runs a post-create bind step, but only when the device binding succeeded.\n\n**Evidence**\n\n`tengu_teleport_client_directory_sync`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}