{"version":"2.1.310","anchor":"auto-mode-read-outside-working-dir-prompt-text-changed-when","canonical_anchor":"auto-mode-read-outside-working-dir-prompt-text-changed-when","heading":"Clearer auto mode warning when the sandbox is not enforcing its rules","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/auto-mode-read-outside-working-dir-prompt-text-changed-when","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Clearer auto mode warning when the sandbox is not enforcing its rules\n\nWhen the sandbox is not enforcing, the auto mode warning now says auto mode asks before each shell command it can't check\n\n**What**\n\nAuto mode lets Claude Code carry on working without asking you about each step. The sandbox is a fenced-off area that limits what shell commands can touch on your machine. When the sandbox is not enforcing its rules, for example because it is off or its file rules are relaxed, Claude Code shows a warning.\n\nThat warning now reads: \"Auto mode asks before each shell command it can't check.\" It used to start with \"Sandboxed commands are not changed on this machine\" and went on to describe the sandbox's state.\n\n**Why**\n\nThe new wording tells you directly what auto mode will do in this situation: it stops and asks you before running any shell command it cannot check.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}