{"version":"2.1.305","anchor":"auto-mode-sandbox-off-reason-text-removed","canonical_anchor":"auto-mode-sandbox-off-reason-text-removed","heading":"Auto mode no longer gives the sandbox as a reason it is unavailable","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/auto-mode-sandbox-off-reason-text-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Auto mode no longer gives the sandbox as a reason it is unavailable\n\nThe message saying auto mode works only inside the sandbox, and to pick a mode in `\/sandbox`, has been removed\n\n**Unclear.** It is not stated whether auto mode still requires the sandbox in the cases this message used to cover.\n\n**What**\n\nClaude 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`.\n\nThe other reasons remain, such as this computer's settings turning auto mode off with `disableAutoMode`.\n\n**Why**\n\nThe sandbox-only limit on running commands without asking may have been dropped, so you may no longer see this reason.\n\n- Area: Auto Mode\n- Names: `\/sandbox`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}