{"version":"2.1.290","anchor":"sandbox-wrap-requires-initialization","canonical_anchor":"sandbox-wrap-requires-initialization","heading":"Sandboxed commands now wait for the sandbox to finish setting up","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/sandbox-wrap-requires-initialization","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Sandboxed commands now wait for the sandbox to finish setting up\n\nClaude Code now makes sure the sandbox is ready before running a command in it, and skips wrapping when no sandbox configuration exists\n\n**Unclear.** It is not shown what Claude Code does with the command when there is no sandbox configuration and it skips wrapping.\n\n**What**\n\nThe sandbox is an isolated environment that limits what a command run by Claude Code can touch. To run a command in it, Claude Code wraps the command in sandbox restrictions. Before wrapping a command, Claude Code now waits for the sandbox to finish starting up. Previously it wrapped the command straight away.\n\nIf no sandbox configuration exists at all, Claude Code no longer wraps the command.\n\n**Why**\n\nA command could previously be wrapped before the sandbox was ready. Waiting for setup to finish stops that from happening.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}