Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Cloud sessions: inactive persistentVolume option, and a directory-sync note for every worktree

Cloud session creation gains a persistentVolume option that is hard-coded off and sends nothing, and the dir-sync prompt notes it applies to every worktree

Group of 2 You'll notice Improvements
JSON All of v2.1.282
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
File SyncArea: what it touches
ImprovementsKind: in v2.1.282,
What probably matters to youSection of the release

What

Two changes touch how cloud sessions are started, for example with --remote:

  • persistentVolume is a new option that now runs from the command-line option parser through cloud and pool session creation into the session-create request. It cannot be turned on. It starts as false, nothing sets it otherwise, and no command-line flag, environment variable or setting feeds it. Even a true value would add nothing to the request, because the helper that should write it (E_r) returns nothing in this build.
  • appliesToEveryWorktree is a new setting for the directory-sync consent dialog, the prompt asking whether your local files may be synced to a cloud session. A worktree is an extra checkout of the same git repository in another folder. When you are in a worktree whose root differs from the repository's main root, the dialog shows a dim note under the repository name: "Your answer applies to every worktree of this repository."

Why

persistentVolume has no effect you can see or use yet. The worktree note matters in practice: allowing or refusing sync from one worktree also decides it for the repository's other worktrees.

Read from
Names in the bundle--remote
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --remote after this was published. To bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio… remote-control see the edit
Confirmed since Anthropic's documentation has since written up --remote, on Continue local sessions from any device with Remote Control. * From `/remote-control`, `claude remote-control`, or `claude --remote-control`: `Couldn't verify your organization's policy for remote control. Check your network connection and try again.` remote-control see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --remote, on Continue local sessions from any device with Remote Control.

See this entry in the whole of v2.1.282 →

Feedback