Configure the sandboxed Bash tool changedsandboxing
Nearest release: v2.1.302, published 8 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 17 Oct 2026 01:27 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 17 Oct 2026 01:37 UTC.
Upstream edited
Recorded here
Lines+12added
Lines−0removed
From line
968
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits50to this page, all time
### `/sandbox` prints `Sandbox settings not changed`
The whole hunk
from line 968, old and new numbered
/
from line 968
968968* **`Command line arguments`**: if you started Claude Code with [`--settings`](/docs/en/settings#change-a-setting-for-one-session), check whether the file or JSON you passed sets one of those keys. If it does, change the value there, or start Claude Code again without those keys.
969969* **`Enterprise managed settings`**: your organization's managed settings are loaded. If they set one of those keys, you can't change that key from `/sandbox` or from any settings file you control, so ask your administrator.
970970
971### `/sandbox` prints `Sandbox settings not changed`
972
973This line means `/sandbox` couldn't save the choice you made in its panel to your project's `.claude/settings.local.json`:
974
975```text theme={null}
976✗ Sandbox settings not changed: /home/you/project/.claude/settings.local.json couldn't be updated (EACCES). Start Claude Code in a project folder you can write to.
977```
978
979If the reason in parentheses is `EACCES`, `EPERM`, or `EROFS`, start Claude Code in a project folder you can write to, then run `/sandbox` again in that session.
980
981If the reason begins with `Invalid JSON syntax in settings file`, correct the JSON in your project's `.claude/settings.local.json`, then run `/sandbox` again.
982
971983## Limitations
972984
973985Sandboxing reduces risk but is not a complete isolation boundary. Review the limitations below before relying on it as a hard security control.
No line in this hunk matches that.