The sandbox is a protected area that limits what commands Claude runs can touch. After you install it on Windows with /sandbox, the follow-up advice now depends on whether your sandbox settings are locked by a higher-priority configuration, such as a --settings file or managed settings set by your organisation:
- Settings locked: Claude Code tells you to run
claude sandbox statusin a terminal and checkinstalledandenabledin its JSON output. - Sandbox off and locked: Claude Code explains that a
--settingsfile or managed settings control it, so/sandboxcannot turn it on. - Status check failed while locked: Claude Code tells you to restart Claude Code to check again.
- Administrator approval cancelled: the message now adds that you can ask your administrator to run the sandbox set-up.
The /sandbox command now returns an error when higher-priority configuration overrides the sandbox settings. Before, the advice always said to run /sandbox to check the current status.
If your organisation manages your settings, /sandbox cannot change them. You are now pointed to steps that can actually help.