{"version":"2.1.318","anchor":"cloud-session-teleport-github-branch-lookup-and-message-cha","canonical_anchor":"cloud-session-teleport-github-branch-lookup-and-message-cha","heading":"Moving a session to the cloud handles GitHub branch checks differently","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/cloud-session-teleport-github-branch-lookup-and-message-cha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Moving a session to the cloud handles GitHub branch checks differently\n\nWhen moving a session to a cloud session, branch checks can ask GitHub, and the no-shared-history message now names the remote's default branch\n\n**Unclear.** Whether the new branch lookup path runs at all, since its condition is switched off in this build.\n\n**What**\n\nWhen Claude Code moves a session to run in the cloud, it checks which git branch the cloud session should start from. Several things changed:\n\n- Branch checks can now always ask GitHub.\n\n- There is a new option to resync when the branch could not be worked out.\n\n- The message shown when your branch shares no history with the remote now names the remote's default branch.\n\n- The log line saying GitHub has no such branch is shorter.\n\n**Why**\n\nThis affects which branch a cloud session starts from.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}