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

Claude Code v2.1.305 ·

Cloud sessions explain sandbox problems and what to do next

New messages tell you when a missing or unusable sandbox affects cloud sessions, with hints pointing to /sandbox and claude apply-project-settings

Group of 2 You'll notice Improvements
JSON All of v2.1.305
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SandboxArea: what it touches
ImprovementsKind: in v2.1.305,
ImprovementsSection of the release

Unclear Where and when these messages are shown, if anywhere yet.

What

A sandbox is a protected area that limits what commands can touch on your machine. Cloud sessions are sessions run on Anthropic's servers. This release adds wording for when the sandbox gets in the way.

  • Unattended mode switched off: a new message (auto_off.reason.sandbox_off) is shown for cloud-session commands that would run without asking you when the machine's sandbox is off.
  • Reason table: a table maps sandbox reasons such as sandbox_unavailable and sandbox_unconfined to short words and a next-step hint. The hints point to /sandbox and to running claude apply-project-settings in the folder "so cloud sessions pick it up". It is paired with the label "Cloud sessions: asking first". No code using this table was seen.

Why

If you control Claude Code from another device, you are told why unattended running switched off and what to run to fix it, instead of being left guessing.

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 doubtWhere and when these messages are shown, if anywhere yet.

See this entry in the whole of v2.1.305 →

Feedback