Unclear Which environments get the new wording is not stated.
What
The sandbox is a restricted environment that shell commands run inside, limiting what they can reach. When a command fails because of it, Claude receives an instruction to briefly explain which restriction probably caused the failure and to mention the /sandbox command. That instruction used to always end with "use the /sandbox command to manage restrictions." It is now built at runtime:
- "change the sandbox settings" is the ending when a condition in the build holds, which applies only in some environments.
- "manage restrictions" is the ending in every other case, as before.
Why
This is a small wording change. In some setups, Claude may now point you at /sandbox as the place to change sandbox settings rather than to manage restrictions.
* Improved `/help` and `/sandbox`: ←/→ and Tab switch tabs from inside a tab's list, and ↓ on an empty Custom commands tab in `/help` no longer leaves the keys stuck until Escsee the edit
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.
Mods aren't sandboxed. If you turn on [sandboxing](/docs/en/sandboxing), the sandbox isolates the Bash commands Claude runs, and a process that a mod starts runs outside it.plugins/mods/overview see the edit
In a tabbed dialog, `tabs:next` and `tabs:previous` switch tabs while the tab row has focus. In some dialogs, such as `/help` and `/sandbox`, the tab-switching keys also work from inside the tab's content.keybindings see the edit
Which environments get the new wording is not stated.
/sandbox on Claude Code changelog