{"version":"2.1.323","anchor":"local-session-move-to-cloud-refactored-resume-or-contin","canonical_anchor":"local-session-move-to-cloud-refactored-resume-or-contin","heading":"Moving a local session to the cloud refuses with a clearer message when a check fails","tier":"notice","area":"Teleport","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/local-session-move-to-cloud-refactored-resume-or-contin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Moving a local session to the cloud refuses with a clearer message when a check fails\n\nIf a session cannot be loaded for a move to the cloud, Claude Code refuses with 'Couldn't load session ... so it wasn't moved', and resuming clears `--continue` too\n\n**What**\n\nYou can move a session on your computer into a cloud session, one that runs on Anthropic's servers, with `--cloud` or `--teleport`. Before the move, Claude Code checks that the session can be moved. If that check fails with an error, Claude Code now refuses with a message like \"Couldn't load session ... so it wasn't moved\". Before, each reason for refusing had its own message written in place.\n\nWhen a cloud session is resumed, Claude Code now clears a `--continue` request as well as a `--resume` request.\n\n**Why**\n\nThis changes how moving a session to the cloud behaves and how it reports a failure.\n\n- Area: Teleport\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}