{"version":"2.1.302","anchor":"cloud-session-start-message-distinguishes-the-ref-the-commit","canonical_anchor":"cloud-session-start-message-distinguishes-the-ref-the-commit","heading":"Moving to the cloud says more precisely which commits stay behind","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/cloud-session-start-message-distinguishes-the-ref-the-commit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Moving to the cloud says more precisely which commits stay behind\n\nThe message about where a cloud session starts now names the branch it checked and says which commits and changes stay local\n\n**What**\n\nWhen you move work to a cloud session, Claude Code tells you which commit the cloud copy starts from. A commit is a saved snapshot in git, and a branch is a named line of commits.\n\nThe message can now name the branch or other reference the commit was found on. It says the session starts from the newest commit that this reference has, and that commits the reference lacks, plus any uncommitted changes, stay on your machine. Before, it named the newest pushed commit and how many commits back it was.\n\n**Why**\n\nYou can see more exactly what reaches the cloud and what stays local.\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"}