{"version":"2.1.319","anchor":"moving-a-session-to-the-cloud-message-for-sessions-ended-by","canonical_anchor":"moving-a-session-to-the-cloud-message-for-sessions-ended-by","heading":"No resume hint when a session Claude ended can't move to the cloud","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/moving-a-session-to-the-cloud-message-for-sessions-ended-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### No resume hint when a session Claude ended can't move to the cloud\n\nIf a session can't move to the cloud because Claude ended it, the error no longer suggests resuming it with claude --resume\n\n**What**\n\nWhen a session cannot be moved to the cloud, the error message usually suggests resuming it locally with `claude --resume`. That suggestion is now left out when the reason is that Claude ended the session. Before, it was left out only when some of the session's history was held back.\n\n**Why**\n\nIt stops Claude Code from telling you to resume a session locally when Claude has already ended it.\n\n- Area: Cloud Sessions\n- Names: `claude --resume`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}