{"version":"2.1.312","anchor":"auto-mode-classification-skipped-for-forwarded-sandbox-host","canonical_anchor":"auto-mode-classification-skipped-for-forwarded-sandbox-host","heading":"Auto mode skips its safety check in one kind of sandbox setup","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/auto-mode-classification-skipped-for-forwarded-sandbox-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Auto mode skips its safety check in one kind of sandbox setup\n\nIn a forwarded sandbox host environment, Claude Code no longer runs auto mode's check on an action and leaves the decision open\n\n**Unclear.** It is not clear when a session counts as a forwarded sandbox host, or what decides the action once the check is skipped.\n\n**What**\n\nIn auto mode, a check decides whether an action can go ahead without asking you. In one kind of environment, called a forwarded sandbox host, Claude Code no longer runs that check. It leaves the decision open instead. A sandbox is a restricted environment for running commands.\n\n**Why**\n\nPermissions are settled differently in this kind of setup, so actions there do not go through auto mode's usual check.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}