{"version":"2.1.287","anchor":"sandbox-bwrap-command-wraps-the-shell-via-a-new-prefix","canonical_anchor":"sandbox-bwrap-command-wraps-the-shell-via-a-new-prefix","heading":"Linux sandbox reports a failure to start as its own kind of error","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/sandbox-bwrap-command-wraps-the-shell-via-a-new-prefix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Linux sandbox reports a failure to start as its own kind of error\n\nOn Linux, a sandboxed command that fails to start is now reported as spawn_failed instead of wrap_failed\n\n**Unclear.** What the text added in front of each sandboxed command contains is not known.\n\n**What**\n\nOn Linux, Claude Code can run commands inside a sandbox, a walled-off space that limits what the command can touch, using a tool called bubblewrap. It now builds the sandboxed command by starting a shell and passing it the command with some text added in front. When the command cannot be started at all, the error is now recorded as `spawn_failed`. Before, it was recorded as `wrap_failed`.\n\n**Why**\n\nThis changes how sandbox failures on Linux are labelled, so a command that never started can be told apart from other sandbox problems.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}