Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Moving a session to the cloud now relaunches with claude --cloud --resume, with clearer refusals

/teleport's move-to-cloud now relaunches Claude Code with --cloud --resume and explains refusals, and the resume hint can show --cloud

Group of 2 You'll notice Nothing to try yet In Development
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
TeleportArea: what it touches
In DevelopmentKind: in v2.1.323,
What probably matters to youSection of the release

What

A 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.

  • 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…'.
  • A new move path checks that moving is allowed, prints 'Moving this session to the cloud…' and relaunches Claude Code as claude --cloud --resume <id>. It carries over --permission-mode, --model, --effort and --disallowed-tools.
  • 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.
  • 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.
  • 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.
  • Each refusal points to claude --cloud --resume as the fallback, and several tell you to run /teleport again.
  • 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.
  • 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.

The 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.

Why

When 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.

Read from
Names in the bundle/teleportclaude --cloud--resume
Feature flag
tengu_teleport_send_to_cloud Off in both readings

The 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.323: 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.323. It isn't a statement about your account. What a flag value here can and cannot tell you

What the documentation says
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed --permission-mode auto or a settings defaultMode: auto starting in a mode that could allow more when auto mode was unavailable. It now…

See this entry in the whole of v2.1.323 →

Feedback