The whole hunk
from line 1690, old and new numbered
/
lines
This page is larger than the 256 KiB this site keeps, so one side of the diff below stops where the stored text does.
from line 1690
16901690
16911691* **Scope**: [`Any file`](#scopes)
16921692* **Type**: array of command patterns
1693* **Default**: unset, so every command Claude Code can sandbox runs sandboxed
1693* **Default**: unset, so no command is excluded
16941694
16951695```json settings.json theme={null}
16961696{
from line 1704
17041704
17051705### `sandbox.allowUnsandboxedCommands`
17061706
1707Let Claude retry a command outside the sandbox with the `dangerouslyDisableSandbox` parameter after the sandbox blocks it. Set it to `false` so Claude Code ignores that parameter completely and every command must run sandboxed or appear in [`excludedCommands`](#sandbox-excludedcommands), which the `/sandbox` **Overrides** tab shows as **Strict sandbox mode**. Use `false` in managed settings for policies that require strict sandboxing.
1707Let Claude retry a command outside the sandbox with the `dangerouslyDisableSandbox` parameter after the sandbox blocks it. Set it to `false` so Claude Code ignores that parameter completely and every command Claude runs must be sandboxed or appear in [`excludedCommands`](#sandbox-excludedcommands). The `/sandbox` **Overrides** tab shows that state as **Strict sandbox mode**. Use `false` in managed settings for policies that require strict sandboxing.
17081708
17091709* **Scope**: [`Any file`](#scopes)
17101710* **Type**: Boolean
17111711 * `true`: Claude can retry a command outside the sandbox with the `dangerouslyDisableSandbox` parameter after the sandbox blocks it
1712 * `false`: Claude Code ignores that parameter, so every command runs sandboxed or appears in `excludedCommands`
1712 * `false`: Claude Code ignores that parameter, so every command Claude runs is sandboxed or appears in `excludedCommands`
17131713* **Default**: `true`
17141714
17151715This enforces strict sandbox mode for everyone the managed settings cover:
from line 1725
17251725
17261726An unsandboxed retry goes through the regular permission flow, with a prompt in Manual mode. See [The unsandboxed retry escape hatch](/docs/en/sandboxing#the-unsandboxed-retry-escape-hatch).
17271727
1728To see when commands you type yourself at the [`!` shell-mode prompt](/docs/en/interactive-mode#shell-mode-with-prefix) run sandboxed, see [strict sandbox mode](/docs/en/sandboxing#the-unsandboxed-retry-escape-hatch).
1729
17281730### `sandbox.filesystem`
17291731
17301732Control which paths sandboxed commands can read and write. By default they can write to the working directory, the session temp directory, and directories you add with `--add-dir`, `/add-dir`, or `permissions.additionalDirectories`, and can read the rest of the filesystem, including credential files. Widen or narrow that with the four path lists, or switch the filesystem layer off with `disabled`. See [Filesystem isolation](/docs/en/sandboxing#filesystem-isolation) for the default boundaries.
from line 3297
32953297}
32963298```
32973299
3298In `"replace"` mode with an empty `verbs` array, Claude Code keeps the built-in verbs.
3299
3300### `statusLine`
3301
3302Run your own command to render a [status line](/docs/en/statusline) below the prompt with context such as the model, cost, or git branch. Optional fields adjust spacing, add periodic re-runs, an
3300In `"replace"` mode with an empty `verbs` array, Claude Code keeps the built-in verbs