What
The sandbox is a restricted environment that limits what commands can reach. Entries in permissions.allow (actions you have approved to run without asking) are converted into sandbox rules. If an entry cannot be worked out during that conversion, Claude Code now reports a configuration error that names the entry. Before, the failure was not handled.
Why
A bad entry is now refused instead of being trusted. The error tells you which entry to fix.
Names in the bundlepermissions.allow
Documented inclaude-code/admin-setup
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Run Claude Code programmatically touched a line naming permissions.allow after this was published.
* **`dontAsk`**: Claude Code denies every call that would otherwise prompt, which is useful for locked-down CI runs. Actions that need no approval in Manual mode still run, such as file reads in your working directories and the [read-only …headless see the edit
Confirmed since
Anthropic's documentation has since written up permissions.allow, on Set up Claude Code for your organization.
| [Permission rules](/docs/en/permissions) | Allow, ask, or deny specific tools and commands | `permissions.allow`, `permissions.deny` |admin-setup see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up permissions.allow, on Set up Claude Code for your organization.
Anthropic's release notes agree
Improved screen-reader output in /mcp: a disabled server is read as "off" instead of "pending"