{"version":"2.1.247","anchor":"file-sync-is-not-offered-when-the-repository-layout-is-unsup","canonical_anchor":"file-sync-is-not-offered-when-the-repository-layout-is-unsup","heading":"File sync is not offered when the repository layout is unsupported","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/file-sync-is-not-offered-when-the-repository-layout-is-unsup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### File sync is not offered when the repository layout is unsupported\n\nFile sync is no longer offered for repository layouts it cannot actually handle.\n\n**What**\n\nBefore offering file sync for a checkout, `claude --cloud` now checks the repository layout and holds the offer back when the layout is not one it can serve, rather than going on to forecast what it would bundle.\n\n**Details**\n\n- The deferral is recorded with the reason `layout_unserved`.\n- The \"not offered\" line now also covers cases where paths cannot be resolved.\n\n**Evidence**\n\n`layout_unserved`\n\n- Area: Cloud Sessions\n- Names: `claude --cloud`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}