{"version":"2.1.309","anchor":"sandbox-post-command-scrub-setup-reordered","canonical_anchor":"sandbox-post-command-scrub-setup-reordered","heading":"Sandbox cleanup after a command runs in a different order","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/sandbox-post-command-scrub-setup-reordered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Sandbox cleanup after a command runs in a different order\n\nFor sandboxed commands, the cleanup that runs after a command now happens earlier, and its failures are no longer logged separately\n\n**What**\n\nA sandbox is a fenced-off space that limits what a command can touch. After a sandboxed command, Claude Code cleans up after it. That cleanup now runs before the other exit and error cleanup is set up. The check for whether a command is sandboxed also happens earlier.\n\n**Why**\n\nA failure in this cleanup step is no longer logged as its own separate message.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}