{"version":"2.1.286","anchor":"cloud-sandbox-refusal-reasons-expanded-seccomp-unavailable","canonical_anchor":"cloud-sandbox-refusal-reasons-expanded-seccomp-unavailable","heading":"More sandbox settings now block serving device tools remotely","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/cloud-sandbox-refusal-reasons-expanded-seccomp-unavailable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### More sandbox settings now block serving device tools remotely\n\nClaude Code now refuses to serve device tools when seccomp is unavailable or more sandbox-weakening settings are on\n\n**Unclear.** It is not confirmed which remote feature uses these device tools.\n\n**What**\n\nThe sandbox limits what commands run by Claude Code can reach. Claude Code refuses to offer its device tools for remote use when the sandbox is missing or has been weakened. Two things changed in how it decides.\n\nIt now refuses with the reason `sandbox_seccomp_unavailable` when seccomp cannot be used. Seccomp is a Linux feature that limits which system operations a program may perform.\n\nThe `sandbox_weakened` reason now also covers these settings:\n\n- `sandbox.enableWeakerNetworkIsolation`\n\n- `sandbox.network.allowLocalBinding`\n\n- a `sandbox.ripgrep` override set anywhere other than managed policy settings\n\nBefore, it covered only `sandbox.allowAppleEvents`, `sandbox.enableWeakerNestedSandbox` and `sandbox.network.allowMachLookup`. The refusal message tells you to open `\/sandbox` and check its Dependencies tab.\n\n**Why**\n\nSome devices that used to serve these tools will now be refused. If that happens, the Dependencies tab in `\/sandbox` shows what is missing.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}