{"version":"2.1.323","anchor":"teleport-move-to-cloud-now-restarts-claude-code-via-claude","canonical_anchor":"teleport-move-to-cloud-now-restarts-claude-code-via-claude","heading":"Moving a session to the cloud now relaunches with claude --cloud --resume, with clearer refusals","tier":"notice","area":"Teleport","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/teleport-move-to-cloud-now-restarts-claude-code-via-claude","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Moving a session to the cloud now relaunches with claude --cloud --resume, with clearer refusals\n\n\/teleport's move-to-cloud now relaunches Claude Code with `--cloud --resume` and explains refusals, and the resume hint can show `--cloud`\n\n**What**\n\nA cloud session is a Claude Code session that runs on Anthropic's servers rather than on your computer. `\/teleport` (also `\/tp`) and the `--teleport` flag connect your terminal with cloud sessions. This release changes how a local session is moved into the cloud and how resuming is suggested.\n\n- The menu no longer starts the restart itself. Before, it showed 'Checking this session, then restarting Claude Code to move it to a new cloud session\u2026'.\n\n- A new move path checks that moving is allowed, prints 'Moving this session to the cloud\u2026' and relaunches Claude Code as `claude --cloud --resume <id>`. It carries over `--permission-mode`, `--model`, `--effort` and `--disallowed-tools`.\n\n- The move is refused, with a specific message, when Claude is still working ('Not moved: Claude is still working. Wait for it to finish, then run \/teleport again.'), when a command is queued, or when a client data URL is set with `--client-data-url` or `CLAUDE_CODE_CLIENT_DATA_URL`.\n\n- It is also refused when input is not an interactive terminal, when Remote Control is keeping messages local, for background sessions, while a task is running ('stop it in \/tasks') and for unsaved sessions.\n\n- It is refused when the session file is missing, when the session ID contains capital letters, or when Claude Code cannot confirm that moving is allowed on this computer, for this account or for its organization.\n\n- Each refusal points to `claude --cloud --resume` as the fallback, and several tell you to run `\/teleport` again.\n\n- New messages cover what stays local (`kept_here`) and limits that are not carried over (`limits_not_carried`). Claude Code also takes a fingerprint of the session's permission settings.\n\n- The 'Resume with:' line printed after a remote session is created now shows `claude --cloud <id>` when an internal check called `ldr` passes, and `claude --teleport <id>` otherwise. Before, it always showed `--teleport`.\n\nThe move is tied to the `tengu_teleport_send_to_cloud` remote switch. The flag server returned off for this site's account and for the anonymous baseline, but no reading has been taken under this release.\n\n**Why**\n\nWhen a session cannot be moved, you are told exactly why and what to do instead. The hint after creating a remote session may now suggest `--cloud` instead of `--teleport`.\n\n- Flag `tengu_teleport_send_to_cloud`: Off in both readings (read for one account on one subscription tier against v2.1.323; 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: Teleport\n- Names: `\/teleport`, `claude --cloud`, `--resume`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}