{"version":"2.1.251","anchor":"eval-runs-that-grant-a-shell-tool-now-refuse-to-run-without-","canonical_anchor":"eval-runs-that-grant-a-shell-tool-now-refuse-to-run-without-","heading":"Eval runs that grant a shell tool now refuse to run without a sandbox","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/eval-runs-that-grant-a-shell-tool-now-refuse-to-run-without-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Eval runs that grant a shell tool now refuse to run without a sandbox\n\nEval runs with a shell tool refuse to start without a sandbox, and hide your credential files.\n\n**What**\n\nEvaluation runs that hand Claude a Bash or PowerShell tool now build a sandbox first and deny access to a long list of credential locations (AWS, GCP, Azure, Docker, Kubernetes, SSH, Kerberos, Maven, Gradle, SBT, npm, pip and more). If the machine has no sandbox backend, or a managed policy turns the sandbox off, the run is refused rather than executed unconfined.\n\n**Details**\n\n- The managed settings consulted are `sandbox.enabled`, `sandbox.failIfUnavailable` and `sandbox.allowUnsandboxedCommands`; weakening any of them produces \"eval shell grant refused: managed policy suppresses the sandbox\".\n- A credential path containing glob characters also causes a refusal, since the denial could not be stated exactly.\n\n**Evidence**\n\n`A shell tool (Bash or PowerShell) was granted but this machine cannot confine it (no sandbox backend on this platform, or it is not installed), so the run was refused rather than run unconfined`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}