{"version":"2.1.247","anchor":"better-explanation-when-a-cloud-checkout-follows-a-branch-ch","canonical_anchor":"better-explanation-when-a-cloud-checkout-follows-a-branch-ch","heading":"Better explanation when a cloud checkout follows a branch change","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/better-explanation-when-a-cloud-checkout-follows-a-branch-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Better explanation when a cloud checkout follows a branch change\n\nWhen your cloud checkout's branch moves, Claude is now told who moved it and whether its commits followed.\n\n**What**\n\nWith `claude --cloud`, when the checkout follows a branch that moved, the note Claude receives now says who moved it, distinguishing a move made by the agent, by you, or by an unknown party, and states whether the agent's own commits came along onto the new branch tip.\n\n**Details**\n\n- The parked \"branch switched\" text no longer opens with \"user switched branches\" when the move was in fact yours, avoiding the redundant preamble.\n\n**Evidence**\n\n`The user switched to ${n}; this checkout followed (it was ${r}).${i}`\n\n- Area: Cloud Sessions\n- Names: `claude --cloud`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}