Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Sandbox set-up messages now always suggest claude sandbox install

Sandbox hints no longer send you to your administrator and always suggest claude sandbox install or /sandbox install instead

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

What

The sandbox is a restricted environment Claude Code can run commands in, controlled with /sandbox. When it needs setting up again, Claude Code's messages no longer send you to your administrator:

  • The guidance about commands excluded from the sandbox, and the hint shown when sandbox set-up fails, used to say your administrator could run the set-up again. They now suggest running claude sandbox install in a terminal, or /sandbox install inside Claude Code. Either way there is one elevation prompt, meaning one request for administrator permission.
  • Whether sandbox settings are locked by policy no longer changes which command is suggested.
  • After the Windows sandbox is removed, the message now always says to run claude sandbox install, or /sandbox install inside Claude Code. The separate message saying set-up was up to your administrator because settings are managed by policy is gone.

Why

On machines where an administrator manages the sandbox, you are now told to set it up yourself rather than to contact them.

See this entry in the whole of v2.1.311 →

Feedback