{"version":"2.1.248","anchor":"sandbox-failure-reason-is-withheld-from-untrusted-output","canonical_anchor":"sandbox-failure-reason-is-withheld-from-untrusted-output","heading":"Sandbox failure reason is withheld from untrusted output","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/sandbox-failure-reason-is-withheld-from-untrusted-output","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Sandbox failure reason is withheld from untrusted output\n\nSandbox startup failure details are hidden from untrusted print-mode output.\n\n**What**\n\nIn print and stream-json modes, when a sandbox is required but cannot be started, the reason is only included in the visible error for trusted invocations. Otherwise you get the bare \"Sandbox required but unavailable\" and the detail goes to the debug log. The full reason is still written to stderr either way.\n\n**Details**\n\n- Trust is decided at runtime from the entrypoint and session; there is no flag to change it.\n\n**Evidence**\n\n`Sandbox required but unavailable`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}