{"version":"2.1.299","anchor":"sandbox-write-check-skipped-when-deny-lists-may-be-short","canonical_anchor":"sandbox-write-check-skipped-when-deny-lists-may-be-short","heading":"Sandbox write check changes when deny lists may be incomplete","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-write-check-skipped-when-deny-lists-may-be-short","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox write check changes when deny lists may be incomplete\n\nThe sandbox's file-write check now returns a negative answer when its stored deny lists may be incomplete, as it already did with sandboxing off\n\n**Unclear.** It is not clear whether the negative answer means affected writes now ask for permission or are handled some other way.\n\n**What**\n\nThe sandbox is a restricted environment that limits what commands Claude runs can touch. One of its checks on file writes already gave a negative answer when sandboxing was turned off. It now also gives a negative answer when the stored deny lists may be incomplete. Deny lists are the lists of places writes are not allowed.\n\n**Why**\n\nThis changes when sandboxed file writes are treated as safe.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}