{"version":"2.1.299","anchor":"sandbox-settings-save-reports-failure","canonical_anchor":"sandbox-settings-save-reports-failure","heading":"Failed sandbox settings saves are no longer recorded as successful","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-settings-save-reports-failure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Failed sandbox settings saves are no longer recorded as successful\n\nWhen saving sandbox settings fails, Claude Code now records it as a failure instead of always recording success\n\n**What**\n\nThe sandbox limits what commands Claude runs can touch, and `\/sandbox` lets you change its settings. When Claude Code saves those settings, it now checks whether the save worked. If it did not, it records a failed save. Before, the result was ignored and the save was always recorded as a success.\n\n**Why**\n\nA sandbox settings change that did not actually get saved is no longer quietly treated as saved.\n\n- Area: Sandbox\n- Names: `\/sandbox`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}