{"version":"2.1.247","anchor":"cloud-session-seeding-names-linked-worktrees-and-split-git-l","canonical_anchor":"cloud-session-seeding-names-linked-worktrees-and-split-git-l","heading":"Cloud-session seeding names linked worktrees and split git layouts as un-seedable","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cloud-session-seeding-names-linked-worktrees-and-split-git-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cloud-session seeding names linked worktrees and split git layouts as un-seedable\n\nStarting a cloud session from a linked worktree now explains why and tells you to use the main checkout.\n\n**What**\n\nStarting a cloud session from a checkout made with `git worktree add`, or from one whose git directory lives outside the working tree, now gets its own refusal and remedy instead of a generic failure. The advice is to start from the repository's main checkout or an ordinary clone.\n\n**Details**\n\n- Two new verdicts, `linked_worktree` and `unserved_layout`, each carry their own explanation text.\n- Both still defer to the repository-too-large message when that was the recorded reason.\n- The seed payloads for the `remote_ref` and `overlay` cases no longer carry a tree hash or the timestamp it was read at.\n\n**Evidence**\n\n`this checkout is a linked working tree (git worktree add), whose commits and changes this machine cannot yet compare with GitHub`\n\n- Area: Cloud Sessions\n- Names: `git worktree add`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}