Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.275 ·

auto-allow-bash-if-sandboxed setting surfaced in diagnostics with its source

Diagnostics now report whether autoAllowBashIfSandboxed is on and where that value came from

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaSandboxwhat it touches
KindImprovementsin v2.1.275,
You'll notice

Diagnostics now report whether autoAllowBashIfSandboxed is on and where that value came from

What

A settings snapshot used for diagnostics and telemetry now reports whether the autoAllowBashIfSandboxed setting is enabled, along with where that value was set from: unsupported, policy, default, or settings.

Why

This makes it easier to see, when diagnosing a session, whether bash commands are being auto-allowed because they're sandboxed, and whether that behavior comes from a policy, a default, or the user's own settings.

Read from
Names in the bundleautoAllowBashIfSandboxed
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.

Confirmed since Anthropic's documentation has since written up autoAllowBashIfSandboxed, on Agent SDK reference - Python. | `autoAllowBashIfSandboxed` | `bool` | `True` | Auto-approve bash commands when sandbox is enabled | agent-sdk/python 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 autoAllowBashIfSandboxed, on Agent SDK reference - Python.

See this entry in the whole of v2.1.275 →