All settings changedsettings-reference
Nearest release: v2.1.252, published 11 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+12added
Lines−12removed
From line
1,581
where the diff opens
First seen
21 Aug 2026
this site's first read of the page
Recorded edits149to this page, all time
The whole hunk
from line 1581, old and new numbered
/
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 1581
15811581}
15821582```
15831583
1584Claude Code takes a Boolean key's value from the highest-precedence settings file that sets it, so a managed `enabled` or `failIfUnavailable` overrides anything a developer sets. It merges array keys across every settings file the session loads, so a developer can append entries; see [Keep developers from widening the policy](/docs/en/sandboxing#keep-developers-from-widening-the-policy) for the managed-only locks. To require the sandbox for an organization, see [Enforce sandboxing with managed settings](/docs/en/sandboxing#enforce-sandboxing-with-managed-settings).
1584Claude Code takes a Boolean key's value from the highest-precedence settings scope that sets it, so a managed `enabled` or `failIfUnavailable` overrides anything a developer sets. It merges array keys across every settings scope the session loads, so a developer can append entries; see [Keep developers from widening the policy](/docs/en/sandboxing#keep-developers-from-widening-the-policy) for the managed-only locks. To require the sandbox for an organization, see [Enforce sandboxing with managed settings](/docs/en/sandboxing#enforce-sandboxing-with-managed-settings).
15851585
15861586### `sandbox.enabled`
15871587
from line 1665
16651665}
16661666```
16671667
1668Excluded commands still go through the regular permission flow. Exclusion is a convenience, not a security boundary: prefer [`filesystem.allowWrite`](#sandbox-filesystem-allowwrite) when a tool only needs to write somewhere specific. Claude Code merges entries across every settings file the session loads, and there is no managed-only lock for this list, so keep a managed list narrow.
1668Excluded commands still go through the regular permission flow. Exclusion is a convenience, not a security boundary: prefer [`filesystem.allowWrite`](#sandbox-filesystem-allowwrite) when a tool only needs to write somewhere specific. Claude Code merges entries across every settings scope the session loads, and there is no managed-only lock for this list, so keep a managed list narrow.
16691669
16701670### `sandbox.allowUnsandboxedCommands`
16711671
from line 1756
17561756}
17571757```
17581758
1759Claude Code merges entries across every settings file the session loads: user, project, local, and managed paths combine rather than replace each other, and Claude Code adds the paths from your `Edit(...)` allow permission rules. An `allowWrite` entry can't lift a [protected path](/docs/en/sandboxing#protected-paths).
1759Claude Code merges entries across every settings scope the session loads: user, project, local, and managed paths combine rather than replace each other, and Claude Code adds the paths from your `Edit(...)` allow permission rules. An `allowWrite` entry can't lift a [protected path](/docs/en/sandboxing#protected-paths).
17601760
17611761### `sandbox.filesystem.denyWrite`
17621762
from line 1778
17781778}
17791779```
17801780
1781Claude Code merges entries across every settings file the session loads, and adds the paths from your `Edit(...)` deny permission rules.
1781Claude Code merges entries across every settings scope the session loads, and adds the paths from your `Edit(...)` deny permission rules.
17821782
17831783### `sandbox.filesystem.denyRead`
17841784
from line 1798
17981798}
17991799```
18001800
1801Claude Code merges entries across every settings file the session loads, and adds the paths from your `Read(...)` deny permission rules. When [`filesystem.disabled`](#sandbox-filesystem-disabled) is `true`, Claude Code doesn't enforce these entries.
1801Claude Code merges entries across every settings scope the session loads, and adds the paths from your `Read(...)` deny permission rules. When [`filesystem.disabled`](#sandbox-filesystem-disabled) is `true`, Claude Code doesn't enforce these entries.
18021802
18031803### `sandbox.filesystem.allowRead`
18041804
from line 1825
18251825
18261826### `sandbox.filesystem.allowManagedReadPathsOnly`
18271827
1828Honor only the [`allowRead`](#sandbox-filesystem-allowread) entries that come from managed settings, so developers can't re-open read access to paths your organization blocked. Claude Code still merges `denyRead` entries from every settings file the session loads.
1828Honor only the [`allowRead`](#sandbox-filesystem-allowread) entries that come from managed settings, so developers can't re-open read access to paths your organization blocked. Claude Code still merges `denyRead` entries from every settings scope the session loads.
18291829
18301830* **Scope**: [`Managed`](#scopes)
18311831* **Type**: Boolean
18321832 * `true`: Claude Code honors only the `allowRead` entries from managed settings
1833 * `false`: `allowRead` entries merge from every settings file the session loads
1833 * `false`: `allowRead` entries merge from every settings scope the session loads
18341834* **Default**: `false`
18351835
18361836This blocks reads of the home directory, re-opens `~/work`, and stops developers from re-opening anything else:
from line 3388
33883388Set the transcript view Claude Code starts in: `"default"`, `"verbose"`, or `"focus"`. When set, it overrides both the sticky `/focus` selection and the [`verbose`](#verbose) setting.
33893389
33903390* **Scope**: [`Any file`](#scopes)
3391* **Type**
3391*
No line in this hunk matches that.