Follow Discord
Sweep 30 Oct 2026 · 21:36Z Build v2.1.315 533 read Stable v2.1.308 Latest v2.1.314 Next v2.1.315 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.315 ·

Sandbox cleanup moves suspicious files aside instead of deleting them

After a sandboxed command, Claude Code now renames planted git-repository files with a .claude-sandbox-quarantine- prefix rather than deleting them

You'll notice Improvements
JSON All of v2.1.315
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SandboxArea: what it touches
ImprovementsKind: in v2.1.315,
ImprovementsSection of the release
What

The 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-.

If the move fails, Claude Code falls back to:

  • removing the entry if it is a symlink, socket or hard link
  • otherwise, setting its permissions to 000 in place so nothing can use it

It 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.

Why

You 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.

See this entry in the whole of v2.1.315 →

Feedback