The /sandbox command now declares explicit requirements metadata, marking itself as interactive (ink) UI only and as not requiring a workspace, matching the pattern used by other local-jsx commands. This affects command availability checks rather than any user-visible text.
Names in the bundle/sandbox
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.
Confirmed since
Anthropic's documentation has since written up /sandbox, on Debug your configuration.
| `Bash(rm *)` deny rule doesn't block `/bin/rm` or `find -delete` | Bash rules match the literal command string, not the underlying executable; see [what a Bash rule doesn't match](/docs/en/permissions#bash-rule-limits) | Use a [PreToolUs…debug-your-config see the edit
Added since
A small documentation edit on Interactive mode touched a line naming /sandbox after this was published.
Unless your session is one of those listed under [strict sandbox mode](/docs/en/sandboxing#the-unsandboxed-retry-escape-hatch), commands you type in shell mode run outside the [sandbox](/docs/en/sandboxing) even when you've enabled sandbox…interactive-mode see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Interactive mode touched a line naming /sandbox after this was published.