{"version":"2.1.299","anchor":"sandbox-command-wrapping-now-restarts-when-config-changes-mi","canonical_anchor":"sandbox-command-wrapping-now-restarts-when-config-changes-mi","heading":"Sandbox rules are rebuilt if settings change while they are prepared","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-command-wrapping-now-restarts-when-config-changes-mi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox rules are rebuilt if settings change while they are prepared\n\nWhen settings change while Claude Code is building a command's sandbox rules, it now starts over instead of using old rules\n\n**What**\n\nA sandbox is a set of limits on what a command run by Claude Code can read and write. Claude Code now notices when your settings change while it is working out a command's file rules, and starts that work again. It also works out read and write rules in the background rather than in one pass, and retries if the Linux sandbox wrapper fails with a particular error.\n\n**Why**\n\nThis stops a command from running under sandbox rules that no longer match your settings.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}