You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Auto ModeArea: what it touches
RemovedKind: in v2.1.305,
RemovedSection of the release
Unclear It is not stated whether auto mode still requires the sandbox in the cases this message used to cover.
What
Claude Code has a set of messages explaining why auto mode is unavailable. One of them has been removed: the one saying that the flag lets commands run without asking only inside the sandbox (a restricted environment for running commands), and to choose a mode in /sandbox.
The other reasons remain, such as this computer's settings turning auto mode off with disableAutoMode.
Why
The sandbox-only limit on running commands without asking may have been dropped, so you may no longer see this reason.
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 sinceAnthropic's documentation has since written up /sandbox, on Configure the sandboxed Bash tool.To see most of these paths resolved for your machine, run `/sandbox` and open the **Config** tab, which lists them under **Denied within allowed**, mixed in with your own `denyWrite` entries.sandboxingsee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated whether auto mode still requires the sandbox in the cases this message used to cover.
Anthropic's documentation agreesAnthropic's documentation has since written up /sandbox, on Configure the sandboxed Bash tool.
