{"version":"2.1.310","anchor":"sandbox-startup-error-message-reworded","canonical_anchor":"sandbox-startup-error-message-reworded","heading":"Sandbox start-up errors no longer always blame missing software","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/sandbox-startup-error-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Sandbox start-up errors no longer always blame missing software\n\nWhen the sandbox cannot start, Claude Code now says so plainly and suggests installing tools only when a tool is actually missing\n\n**What**\n\nThe sandbox is a restricted area Claude Code can run commands in. When it is switched on but fails to start, the warning used to always say dependencies were missing and suggest installing tools such as `bubblewrap` and `socat`. Now:\n\n- if an error says something is not installed or not found, or you are on Windows, the warning still says dependencies are missing and shows the install hint\n\n- otherwise it says \"sandbox is enabled but cannot start here\", with no install hint\n\n- the detailed error now reads \"The sandbox cannot run on this machine yet:\" followed by the reasons\n\n**Why**\n\nThe old message could send you off installing packages when something else was the real problem. The new wording points you at the actual cause.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}