{"version":"2.1.309","anchor":"sandbox-settings-listing-no-longer-excludes-a-path","canonical_anchor":"sandbox-settings-listing-no-longer-excludes-a-path","heading":"Sandbox settings no longer leave out one path","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/sandbox-settings-listing-no-longer-excludes-a-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Sandbox settings no longer leave out one path\n\nThe list of sandbox settings now keeps every sandbox entry instead of dropping one excluded path\n\n**Unclear.** Which setting used to be left out, and where this list is shown or used, is not clear.\n\n**What**\n\nThe sandbox is the walled-off area that limits what Claude Code's commands can reach. When Claude Code picks out the sandbox settings, it now keeps every entry under the sandbox section. In earlier builds it also dropped the entries for one specific path.\n\n**Why**\n\nMore sandbox settings may now be listed or applied than before.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}