{"version":"2.1.319","anchor":"cloud-move-refusal-for-agent-sessions-now-suggests-claude","canonical_anchor":"cloud-move-refusal-for-agent-sessions-now-suggests-claude","heading":"Refusing to move an agent session to the cloud now suggests starting one there","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/cloud-move-refusal-for-agent-sessions-now-suggests-claude","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Refusing to move an agent session to the cloud now suggests starting one there\n\nWhen a session cannot move to the cloud because the cloud lacks its agent, the message now suggests `claude --cloud \"your task\"`\n\n**What**\n\nA cloud session is a Claude Code session that runs on Anthropic's servers instead of your computer. If you try to move a session to the cloud while it is running as an agent the cloud session would not have, Claude Code refuses and keeps the session where it is. That message used to end with \"It stays here.\" It now adds that a new conversation can go to the cloud, and shows how: `claude --cloud \"your task\"`.\n\nA value that was filled into this message wrongly before is also fixed.\n\n**Why**\n\nThe refusal now gives you a next step instead of a dead end.\n\n- Area: Cloud Sessions\n- Names: `claude --cloud`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}