{"version":"2.1.318","anchor":"remote-can-check-a-local-session-move-before-creating-the","canonical_anchor":"remote-can-check-a-local-session-move-before-creating-the","heading":"Moving a local session to the cloud with --remote can now be refused","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/remote-can-check-a-local-session-move-before-creating-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Moving a local session to the cloud with --remote can now be refused\n\nBefore `--remote` creates a cloud session, Claude Code can check whether moving your local session is allowed and stop if it is not\n\n**Unclear.** It is not clear what causes this check to run, so it is unknown which `--remote` launches it applies to.\n\n**What**\n\n`--remote` is the older name for `--cloud`, the option that starts a session on Anthropic's servers instead of your computer. Before it creates that session, it can now check whether moving your local session to the cloud is allowed. If the move is not allowed, Claude Code stops with a refusal error and does not create the session. In some cases the move is sent to a shared pool of machines meant for monorepos, which are single repositories holding many projects.\n\n**Why**\n\nIf you use `--remote` or `--cloud` to carry on local work in the cloud, the move can now be turned down before it starts.\n\n- Area: Cloud Sessions\n- Names: `--remote`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: yes"}