{"version":"2.1.295","anchor":"sandbox-cleanup-renamed-and-takes-a-new-option-fanbudget-d","canonical_anchor":"sandbox-cleanup-renamed-and-takes-a-new-option-fanbudget-d","heading":"Sandbox cleanup after a command was reworked","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/sandbox-cleanup-renamed-and-takes-a-new-option-fanbudget-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Sandbox cleanup after a command was reworked\n\nThe cleanup Claude Code runs after a sandboxed command was renamed and now takes a setting to skip its scrubbing step\n\n**Unclear.** What this changes for someone running commands in the sandbox is not clear.\n\n**What**\n\nThe sandbox limits what files and network access commands run by Claude can reach. After a command runs, Claude Code cleans up. One version of that cleanup now skips its scrubbing step entirely, where before it spared certain git objects and references. The main cleanup now also passes on whether the command wrote only to its own scratch area. A separate comparison of usage budgets was removed.\n\n**Why**\n\nThis may change when sandboxed shell commands clean up paths in bare git repositories, which are git repositories with no working copy of the files.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}