Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

Sandbox excludedCommands description now spells out what stays sandboxed

The excludedCommands description now says a call leaves the sandbox only if every command in it matches, and lists cases that stay inside

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

The description of the sandbox excludedCommands setting is more precise now. The sandbox is a fenced-off space where commands run with limited access. The description used to say only that matching command patterns always run outside it.

It now says an entry takes a call out of the sandbox only when every command in the call matches an entry. This includes every part of a pipe or chain. It also lists calls that stay sandboxed:

  • cd
  • command substitution, such as $(...)
  • redirects other than 2>&1, including heredocs
Why

The old wording suggested more commands would escape the sandbox than actually do. If you rely on excludedCommands, check that your pipes, chains and redirects match these rules.

Read from
Names in the bundleexcludedCommands

See this entry in the whole of v2.1.314 →

Feedback