{"version":"2.1.293","anchor":"move-to-cloud-adds-callbacks-and-consolidated-error-handling","canonical_anchor":"move-to-cloud-adds-callbacks-and-consolidated-error-handling","heading":"Moving a session to the cloud now reports when the outcome is unclear","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/move-to-cloud-adds-callbacks-and-consolidated-error-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Moving a session to the cloud now reports when the outcome is unclear\n\nMoving a session to the cloud now tells the caller when it moved, may have moved or was refused, and treats server errors as possibly moved\n\n**What**\n\nWhen Claude Code moves a session to the cloud, so it keeps running on a remote machine, it now reports three outcomes to the part of Claude Code that asked: moved, may have moved, and refused. A server error, or the reply that the session is already on cloud, now counts as may have moved. Before, the request only returned messages.\n\n**Why**\n\nA move can fail in a way that leaves it unclear whether the session moved. Treating those cases as possibly moved lets Claude Code act on that instead of assuming the move failed.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}