{"version":"2.1.307","anchor":"bare-repo-scrub-helper-in-sandbox","canonical_anchor":"bare-repo-scrub-helper-in-sandbox","heading":"Sandbox cleanup of planted bare Git repositories was reworked","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/bare-repo-scrub-helper-in-sandbox","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Sandbox cleanup of planted bare Git repositories was reworked\n\nClaude Code's sandbox cleanup of planted bare-repository files has changed, falling back to removing empty folders or the whole directory\n\n**What**\n\nThe sandbox is a restricted space where Claude Code runs commands with limited access to your system. A bare repository is a Git repository without a working copy of files, made of entries such as `HEAD`, `objects` and `refs`. Claude Code's cleanup that removes such files when they have been planted has changed. It removes those files, then falls back to removing empty folders, or the whole directory if a `HEAD` file is still there. It logs each file it removes.\n\n**Why**\n\nIt hardens the sandbox against files placed to trick Git into treating a folder as a repository.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}