{"version":"2.1.242","anchor":"cloud-sessions-can-be-seeded-from-a-bundle-of-your-local-com","canonical_anchor":"cloud-sessions-can-be-seeded-from-a-bundle-of-your-local-com","heading":"Cloud sessions can be seeded from a bundle of your local commits","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/cloud-sessions-can-be-seeded-from-a-bundle-of-your-local-com","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Cloud sessions can be seeded from a bundle of your local commits\n\nA cloud session can start from your local commits instead of always pulling the remote copy.\n\n**What**\n\nWhen your checkout agrees with the pinned remote commit, a cloud session can now be started from a git bundle of your local HEAD instead of refusing and falling back to the remote's copy. What decides whether this is offered at all is set outside the code paths visible here, and it degrades cleanly to the old seeding when unavailable.\n\n**Details**\n\n- The seed carries the pinned commit, your local head commit, the agreed tree and a digest of the bundle.\n- The planner is loaded on demand; if that load fails the plan is reported unavailable and normal seeding proceeds.\n- New refusal reasons include pull not supported, the head having moved during planning, and the file inventory being refused.\n- Tracked files are written through a temporary file created exclusively, with the parent directory re-verified as being under the sync root.\n- Emits `tengu_ccr_overlay_bundle`.\n\n**Evidence**\n\n`tengu_ccr_overlay_bundle`, `planOverlay`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}