{"version":"2.1.275","anchor":"auto-allow-bash-if-sandboxed-setting-surfaced-in-diagnostics","canonical_anchor":"auto-allow-bash-if-sandboxed-setting-surfaced-in-diagnostics","heading":"auto-allow-bash-if-sandboxed setting surfaced in diagnostics with its source","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/auto-allow-bash-if-sandboxed-setting-surfaced-in-diagnostics","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### auto-allow-bash-if-sandboxed setting surfaced in diagnostics with its source\n\nDiagnostics now report whether autoAllowBashIfSandboxed is on and where that value came from\n\n**What**\n\nA settings snapshot used for diagnostics and telemetry now reports whether the `autoAllowBashIfSandboxed` setting is enabled, along with where that value was set from: `unsupported`, `policy`, `default`, or `settings`.\n\n**Why**\n\nThis makes it easier to see, when diagnosing a session, whether bash commands are being auto-allowed because they're sandboxed, and whether that behavior comes from a policy, a default, or the user's own settings.\n\n- Area: Sandbox\n- Names: `autoAllowBashIfSandboxed`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}