{"version":"2.1.318","anchor":"move-a-local-session-to-the-cloud-by-copy-teleport-claude","canonical_anchor":"move-a-local-session-to-the-cloud-by-copy-teleport-claude","heading":"Move a local session to the cloud by copy","tier":"use","area":"Cloud Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/move-a-local-session-to-the-cloud-by-copy-teleport-claude","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Move a local session to the cloud by copy\n\nA new path moves a local session to a cloud session by copying its recent turns, via \/teleport and claude --cloud, with many safety checks\n\n**Unclear.** It is not clear whether `\/teleport` or `--cloud` reach this move for anyone using this version, since the feature depends on a remote switch.\n\n**What**\n\nNew code lets you move a local session to a cloud session, one that runs on Anthropic's servers instead of your computer. A session is one conversation with Claude. The move copies a plain-text version of the session's newest turns.\n\n- It is reached from the `\/teleport` menu as a 'send by copy' option and from launching with `--remote` or `--cloud`. A matching `--resume` request is handled as a move too.\n\n- Before moving, it checks that the account matches the one on record. It also checks for no turns from a third-party provider, no Remote Control history hold, nothing else currently holding the session, no `dontAsk` mode, and no launch flags it cannot carry. Each failed check refuses with its own message.\n\n- The cloud side gets a handoff message and the conversation as an attached file. Account memory and summaries are not sent.\n\n- A screen titled `Move this session to the cloud` asks `What should Claude do next? The cloud session starts when you send this.` and has a box to type in.\n\n- The move saves the transcript, checks the session was not already moved elsewhere, and restarts Claude Code with `--cloud <id>`. It carries over plan mode, model, effort and the disallowed-tools list, and sets `CLAUDE_CODE_TELEPORT_MOVE=1` so the restart knows it follows a move. If the restart fails it falls back to `--resume`.\n\n- It can be offered without Remote Control. When Remote Control is connected and this move is not available, the older path is used, gated by `tengu_teleport_send_to_cloud`.\n\n- New failure messages include 'Not moved to the cloud: this session's permissions changed during the move' and 'Not moved. To continue it here, run `claude --resume ...`'.\n\n- The whole move is gated by the `tengu_woolly_blanket` flag and by an organization or policy check.\n\nOne branch is not finished. Before a remote session is created, `askMoveFirstMessage` asks for the first message, and the 'wasn't moved' notice it then checks is fixed to empty, so that branch never runs.\n\n**Why**\n\nThis would let you hand a session you started on your computer to the cloud and keep going there, without carrying over account memory. Part of the flow is still stubbed out, and nothing here says the move is available to you.\n\n- Flag `tengu_woolly_blanket`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Flag `tengu_teleport_send_to_cloud`: Off in both readings (read for one account on one subscription tier against v2.1.318; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: yes"}