{"version":"2.1.290","anchor":"sandbox-config-changes-during-startup-are-re-applied-awspa","canonical_anchor":"sandbox-config-changes-during-startup-are-re-applied-awspa","heading":"Sandbox setting changes made during startup are no longer lost","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/sandbox-config-changes-during-startup-are-re-applied-awspa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Sandbox setting changes made during startup are no longer lost\n\nSandbox setting changes that arrive while the sandbox is starting are now applied afterwards, and `awsPairs` accepts a single entry\n\n**What**\n\nThe sandbox is the restricted environment Claude Code can run commands in. If its settings changed while the sandbox was still starting up, that change used to be lost. Claude Code now applies it once startup finishes, and stops the starting values from being loaded again over it once the sandbox is running.\n\nThe `awsPairs` sandbox setting now accepts a single entry as well as a list of entries.\n\n**Why**\n\nA settings change made at the wrong moment no longer silently disappears, so the sandbox runs with the configuration you set.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}