Moving a local session to the cloud refuses with a clearer message when a check fails
If 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
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TeleportArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
What
You 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.
When a cloud session is resumed, Claude Code now clears a --continue request as well as a --resume request.
Why
This changes how moving a session to the cloud behaves and how it reports a failure.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed claude --teleport opening an empty session when the server could not find the session's history, and claude -p --teleport exiting…
