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 ·

Settings schema now describes sandbox.excludedCommands

The settings schema now explains that sandbox.excludedCommands is a convenience, not a security boundary, and that its patterns merge across sources

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

The settings schema (the description of valid settings that editors use for hints and checking) now explains sandbox.excludedCommands. Before, the entry had no description. It now says:

  • the entries are command patterns, written like Bash permission rules, that always run outside the sandbox
  • it is a convenience, not a security boundary, and excluded commands still go through the permission flow
  • patterns from different settings sources are merged together
Why

Editors that read the schema now show this explanation, making clear that excluding a command from the sandbox does not skip permission prompts.

Read from
Names in the bundlesandbox.excludedCommands
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged sandbox.excludedCommands to ignore project and local settings entries when managed settings or --settings set…

See this entry in the whole of v2.1.282 →

Feedback