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.
What
New 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.
- It is reached from the
/teleportmenu as a 'send by copy' option and from launching with--remoteor--cloud. A matching--resumerequest is handled as a move too. - 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
dontAskmode, and no launch flags it cannot carry. Each failed check refuses with its own message. - The cloud side gets a handoff message and the conversation as an attached file. Account memory and summaries are not sent.
- A screen titled
Move this session to the cloudasksWhat should Claude do next? The cloud session starts when you send this.and has a box to type in. - 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 setsCLAUDE_CODE_TELEPORT_MOVE=1so the restart knows it follows a move. If the restart fails it falls back to--resume. - 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. - 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 ...'. - The whole move is gated by the
tengu_woolly_blanketflag and by an organization or policy check.
One 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.
Why
This 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.
tengu_woolly_blanket Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.318: 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.
tengu_teleport_send_to_cloud Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.318: 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.
Read once, for one account on one subscription tier, against v2.1.318. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear whether `/teleport` or `--cloud` reach this move for anyone using this version, since the feature depends on a remote…
New in this build: tengu_woolly_blanket