{"version":"2.1.319","anchor":"cloud-move-hands-off-a-summary-instead-of-the-conversation-f","canonical_anchor":"cloud-move-hands-off-a-summary-instead-of-the-conversation-f","heading":"Moving a session to the cloud now sends a summary, with new refusal messages","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/cloud-move-hands-off-a-summary-instead-of-the-conversation-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Moving a session to the cloud now sends a summary, with new refusal messages\n\nclaude --cloud moves now hand off a conversation summary instead of the conversation file, and explain when a move is refused\n\n**Unclear.** It is not stated whether every cloud move works this way or only moves where a server-side switch turns it on.\n\n**What**\n\nYou can move a local session (one conversation with Claude) to a cloud session with `--cloud`. The move now sends a summary of the conversation instead of attaching the conversation as a file.\n\n- The notice now says Claude in the cloud has a summary, \"not the conversation itself\". Before, it said Claude had \"its newest messages, with the conversation as a file to read\", and the conversation was sent as an attached file.\n\n- If the conversation is too long, the error tells you to run `\/compact` in `claude --resume` first.\n\n- If logging in failed, it tells you to log in first.\n\n- If the conversation changed after the summary was made, the move is refused.\n\nClaude Code also records whether a summary was carried over.\n\n**Why**\n\nA session moved to the cloud starts from a summary only, so Claude there may know less of the older history. The new messages tell you what to do when a move does not go through.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}