Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.299 ·

The sandbox retries when it fails to start, and refuses commands it cannot protect

If the sandbox fails to start, Claude Code retries without real-path twins, and otherwise refuses commands that would run inside it

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

The sandbox is a restricted environment that limits what commands run by Claude Code can touch. Claude Code now handles a sandbox that will not start differently:

  • If starting fails while extra path entries that Claude Code calls real-path twins are listed, it switches those off and tries again. They stay off until your settings change.
  • If the sandbox still cannot start, Claude Code shows "Sandbox is enabled but failed to initialize" and refuses any command that would have run inside the sandbox until it can start.
  • When the working folder is one the sandbox refuses to run in, commands that would run in the sandbox are refused too.

Before, Claude Code either stopped with "Sandbox is required but failed to initialize" or turned the sandbox off for the rest of the session.

Separately, when Claude Code fetches missing parts of a partially cloned git repository, it now reports whether the fetch worked first time, needed a retry, or was skipped.

Why

The sandbox is a safety boundary, and this changes what happens when it breaks. Instead of carrying on with the sandbox switched off, Claude Code now blocks the commands it cannot protect, so you may see refusals where before commands simply ran.

See this entry in the whole of v2.1.299 →

Feedback