{"version":"2.1.288","anchor":"remote-session-create-attaches-launch-checkout-for-bundle-to","canonical_anchor":"remote-session-create-attaches-launch-checkout-for-bundle-to","heading":"Remote sessions can attach the launch checkout when sending a bundle","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-session-create-attaches-launch-checkout-for-bundle-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote sessions can attach the launch checkout when sending a bundle\n\nCreating a remote session now attaches the local checkout you launched from even when your code is sent as a bundle\n\n**Unclear.** It is not clear what difference the 'remote' and 'bundle' markings make to the remote session.\n\n**What**\n\nWhen Claude Code creates a remote session, it can describe the local checkout you launched from. A remote session is one that runs on another machine instead of yours, and a checkout is your local copy of a code repository. Before this change, that description was attached only when your code was not being sent as a bundle, a packaged copy of the repository. It is now also attached when a bundle is sent, and marked as covering either the remote repository or the bundle.\n\n**Why**\n\nThis affects how sessions are set up when you move work to a remote machine.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}