[DOCS] Sandbox settings reference omits `sandbox.filesystem.disabled`

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

The Sandbox settings section, together with the Configure sandboxing section of the sandbox guide.

Current Documentation

The settings reference currently introduces the section as:

"Configure advanced sandboxing behavior. Sandboxing isolates bash commands from your filesystem and network."

The reference lists enabled, failIfUnavailable, autoAllowBashIfSandboxed, excludedCommands, allowUnsandboxedCommands, and several filesystem.* and network.* keys, but it does not list filesystem.disabled.

The sandbox guide currently describes the filesystem controls as allowing or denying paths, for example:

"By default, sandboxed commands can write only to the current working directory and the session temp directory."

It then documents sandbox.filesystem.allowWrite, sandbox.filesystem.denyWrite, sandbox.filesystem.denyRead, and sandbox.filesystem.allowRead, but does not explain how to disable filesystem isolation while retaining network isolation.

What's Wrong or Missing?

Claude Code 2.1.216 adds the sandbox.filesystem.disabled setting to skip filesystem isolation while keeping network egress control. The live settings reference has no entry for this new key, and the sandbox guide has no syntax, example, scope, or security explanation for it.

This leaves users who need network egress restrictions without filesystem isolation unable to discover the supported configuration or understand how it interacts with sandbox.enabled, the existing filesystem allow/deny keys, permission rules, and the network allowlist. It also leaves the current statement that sandboxing isolates Bash commands from both the filesystem and network without explaining this supported filesystem-only exception.

Suggested Improvement

Add sandbox.filesystem.disabled to the Sandbox settings table with a minimum-version marker for Claude Code 2.1.216 or later. Explain that enabling it disables the sandbox's filesystem isolation while preserving the sandbox network boundary and network egress controls, and document whether the setting is effective only when sandbox.enabled is true.

Add a configuration example to the sandbox guide, such as:

{
  "sandbox": {
    "enabled": true,
    "filesystem": {
      "disabled": true
    },
    "network": {
      "allowedDomains": ["api.example.com"]
    }
  }
}

The guide should include a warning that this mode does not provide filesystem isolation, so users should choose it only when they intentionally want the network boundary without the filesystem boundary. It should also clarify how filesystem.disabled affects the existing allowWrite, denyWrite, denyRead, and allowRead settings.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/settings | 401-413 | Sandbox settings reference lists neighboring keys but omits filesystem.disabled |
| https://code.claude.com/docs/en/sandboxing | 145-176 | Sandboxing configuration explains filesystem path controls but not the filesystem-isolation toggle |
| https://code.claude.com/docs/en/changelog | 13-14 | Claude Code 2.1.216 release entry announces sandbox.filesystem.disabled |

Total scope: 2 operational documentation pages are affected, with the changelog entry serving as the release cross-reference.

The platform documentation mirror contains managed-agent and self-hosted-sandbox material, but this setting is a Claude Code local sandbox setting and the relevant operational documentation belongs on code.claude.com.