{"version":"2.1.301","anchor":"settings-validation-sandboxcredentials-warnings-now-handle","canonical_anchor":"settings-validation-sandboxcredentials-warnings-now-handle","heading":"Sandbox credential settings errors are now checked separately","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/settings-validation-sandboxcredentials-warnings-now-handle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Sandbox credential settings errors are now checked separately\n\nProblems in sandbox and sandbox.credentials settings, including warnings, are now judged by their own check for whether they stop settings from loading\n\n**Unclear.** It is not clear whether any settings that loaded before will now be stopped, or the other way round.\n\n**What**\n\nThe sandbox limits what commands run by Claude can reach. When your settings have a problem, Claude Code decides whether it is serious enough to stop the settings from loading.\n\nThat decision is now split into two checks:\n\n- A new check treats any error as blocking, along with warnings on `sandbox`, `sandbox.credentials` and `sandbox.credentials.files`.\n\n- The older check, which also treats problems in permissions and `sandbox.filesystem` settings as blocking, no longer handles the credential cases.\n\nBefore, one check treated a problem as blocking when it was more than a warning, or when it was on `sandbox` or `sandbox.credentials`.\n\n**Why**\n\nThis may change which mistakes in your sandbox or permission settings stop those settings from loading. If you use `sandbox.credentials.files`, a warning there may now count as blocking.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}