{"version":"2.1.302","anchor":"cloud-session-launch-checks-github-for-branch-existence-and","canonical_anchor":"cloud-session-launch-checks-github-for-branch-existence-and","heading":"Cloud sessions warn when your branch is not on GitHub","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/cloud-session-launch-checks-github-for-branch-existence-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Cloud sessions warn when your branch is not on GitHub\n\nBefore starting a cloud session, Claude Code asks GitHub whether your branch exists there, and warns that it will use the default branch if not\n\n**What**\n\nA cloud session runs on a remote machine instead of your own computer. When you start one, Claude Code now asks GitHub whether your current branch exists there. A branch is a named line of work in your code. If it has not been pushed, you see a warning: Branch X is not on GitHub, so the cloud session starts from the default branch.\n\nOther changes:\n\n- Sessions started with no repository are now marked as started empty.\n\n- Notices about the code bundle sent to the session can now be shown as warnings.\n\n**Why**\n\nThis changes which code the cloud session starts from. If you have not pushed your branch, the session works on the default branch and not on your changes.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}