Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 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 Nothing to try yet No documentation found In Development
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
Cloud SessionsArea: what it touches
In DevelopmentKind: 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 bundlepersistentVolume
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not confirmed that every way of creating a cloud session takes this value only from the launch options.

See this entry in the whole of v2.1.282 →

Feedback