{"version":"2.1.302","anchor":"sandbox-config-install-now-wraps-failures","canonical_anchor":"sandbox-config-install-now-wraps-failures","heading":"Sandbox setup failures now come with a named error","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/sandbox-config-install-now-wraps-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Sandbox setup failures now come with a named error\n\nIf Claude Code cannot install its sandbox settings, the error is now labelled as a failed install instead of passed on unlabelled\n\n**What**\n\nThe sandbox is the fenced-off area that limits which files and network access commands can reach. When Claude Code fails to apply new sandbox settings, it now reports the failure with the label `configNotInstalled`. It used to pass the error on unlabelled. The sandbox warnings about blocked file reads now also go through Claude Code's standard message system.\n\n**Why**\n\nA sandbox failure is now identified by its kind, so it can be told apart from other errors.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}