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 ·

Stricter safety check for complex shell commands

The check that lets some shell commands run without asking now refuses more risky patterns, including file patterns that may match nothing

Nothing to try yet In Development
JSON All of v2.1.315
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Bash SafetyArea: what it touches
In DevelopmentKind: in v2.1.315,
In DevelopmentSection of the release

Unclear It is not stated whether a command refused by this check is put to you for approval or blocked outright.

What

Before running some shell commands without asking you, Claude Code reads them to make sure they are safe. That check is now stricter:

  • It refuses an unquoted pattern such as *.txt placed before ssh, gcloud or similar commands, because a pattern that matches no file, or an empty value, can vanish and let the next word take its place. The message tells you to quote it or name the files.
  • It warns about the --ssh-flag and --scp-flag options of gcloud.
  • It handles exec commands in the style of kubectl exec.
  • It refuses typeset -i and typeset -F declarations of special variable names.
  • It no longer treats variables that bash or zsh set themselves as harmless.

Claude Code's built-in default turns these extra checks on, though the server can change that.

Why

More compound shell commands will stop passing this automatic check. To get past it, quote patterns or list files by name.

Read from
Feature flag
tengu_hollow_sandpiper Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.315: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.315. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated whether a command refused by this check is put to you for approval or blocked outright.

See this entry in the whole of v2.1.315 →

Feedback