{"version":"2.1.315","anchor":"sandbox-post-command-scrub-quarantines-planted-entries-inste","canonical_anchor":"sandbox-post-command-scrub-quarantines-planted-entries-inste","heading":"Sandbox cleanup moves suspicious files aside instead of deleting them","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/sandbox-post-command-scrub-quarantines-planted-entries-inste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Sandbox cleanup moves suspicious files aside instead of deleting them\n\nAfter a sandboxed command, Claude Code now renames planted git-repository files with a `.claude-sandbox-quarantine-` prefix rather than deleting them\n\n**What**\n\nThe sandbox limits what a command run by Claude Code can touch. After a sandboxed command finishes, Claude Code checks for files or folders the command may have planted that would make a folder look like a bare git repository, one with no working files. Instead of deleting such an entry, Claude Code now moves it aside whole under a name starting with `.claude-sandbox-quarantine-`.\n\nIf the move fails, Claude Code falls back to:\n\n- removing the entry if it is a symlink, socket or hard link\n\n- otherwise, setting its permissions to `000` in place so nothing can use it\n\nIt also gives the owner back full access to a folder whose permissions the command had changed. It does nothing if the folder containing the entry now points somewhere other than where it did when the sandbox was set up. This applies where the sandbox is active, outside Windows.\n\n**Why**\n\nYou may find files or folders named `.claude-sandbox-quarantine-*` in your repositories after sandboxed commands. A file that was already there before is no longer silently deleted, so you can inspect it and restore it if it was yours.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}