{"version":"2.1.78","anchor":"sandbox-unavailability-warnings","canonical_anchor":"sandbox-unavailability-warnings","heading":"Sandbox Unavailability Warnings","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.78\/e\/sandbox-unavailability-warnings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.78","markdown":"### Sandbox Unavailability Warnings\n\n**What**\n\nClaude Code now proactively detects when sandboxing is configured but cannot actually run, and displays a clear warning at startup instead of silently falling back.\n\n**Details**\n\n- Checks for missing dependencies (bubblewrap, socat on Linux; ripgrep), unsupported platforms, and WSL1 incompatibility\n- Displays a warning: `\u26a0 Sandbox disabled: {reason}` followed by `Commands will run WITHOUT sandboxing. Network and filesystem restrictions will NOT be enforced.`\n- The `\/sandbox` diagnostic UI now also shows ripgrep status and uses \"seatbelt: built-in (macOS)\" labeling on macOS\n\n**Evidence**\n\nSandbox check function (search for `\"getSandboxUnavailableReason\"`) and startup warning (search for `\"Commands will run WITHOUT sandboxing\"`)"}