{"version":"2.1.299","anchor":"sandbox-credentials-schema-wording-stderr-writes-may-be-dro","canonical_anchor":"sandbox-credentials-schema-wording-stderr-writes-may-be-dro","heading":"Sandbox credential paths described like denyRead, and error output may be dropped","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-credentials-schema-wording-stderr-writes-may-be-dro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox credential paths described like denyRead, and error output may be dropped\n\nThe sandbox credential path setting now says it accepts the same path forms as filesystem.denyRead, and error output may be dropped when busy\n\n**What**\n\nThe sandbox is the restricted space Claude Code runs commands in. Two things changed around it:\n\n- The description of the sandbox setting for credential paths now says it supports the same path forms as a string in `filesystem.denyRead`.\n\n- Text written to the error output stream (stderr, where programs print error messages) through the sandbox may now be dropped when output is under pressure.\n\n**Why**\n\nError output from the sandbox is no longer guaranteed to arrive in full, so a missing line there does not always mean nothing was printed.\n\n- Area: Sandbox\n- Names: `denyRead`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}