{"version":"2.1.317","anchor":"sandbox-retries-a-failed-start-once-when-starts-failed-befor","canonical_anchor":"sandbox-retries-a-failed-start-once-when-starts-failed-befor","heading":"Sandbox tries to start again after an earlier failed start","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sandbox-retries-a-failed-start-once-when-starts-failed-befor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Sandbox tries to start again after an earlier failed start\n\nIf the sandbox failed to start before, the next sandboxed command now waits for a fresh start attempt\n\n**Unclear.** Whether this retry runs for everyone or only behind a switch is not clear.\n\n**What**\n\nThe sandbox limits what commands Claude runs can reach. If an earlier attempt to start it failed, the next command that needs it now waits for a fresh start attempt. A related log line also changed. Some extra paths it may add are now off only for that attempt, and stay off only if the attempt works. Before, they stayed off until your settings changed.\n\n**Why**\n\nThe sandbox can now recover from a start failure that was only temporary, without you changing settings.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}