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 messages give the right advice when settings are locked by policy

After setting up the sandbox on Windows, Claude Code no longer sends you to /sandbox when policy-controlled settings stop it from helping

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 protected area that limits what commands Claude runs can touch. After you install it on Windows with /sandbox, the follow-up advice now depends on whether your sandbox settings are locked by a higher-priority configuration, such as a --settings file or managed settings set by your organisation:

  • Settings locked: Claude Code tells you to run claude sandbox status in a terminal and check installed and enabled in its JSON output.
  • Sandbox off and locked: Claude Code explains that a --settings file or managed settings control it, so /sandbox cannot turn it on.
  • Status check failed while locked: Claude Code tells you to restart Claude Code to check again.
  • Administrator approval cancelled: the message now adds that you can ask your administrator to run the sandbox set-up.

The /sandbox command now returns an error when higher-priority configuration overrides the sandbox settings. Before, the advice always said to run /sandbox to check the current status.

Why

If your organisation manages your settings, /sandbox cannot change them. You are now pointed to steps that can actually help.

Read from
Names in the bundle/sandbox--settings

See this entry in the whole of v2.1.311 →

Feedback