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 ·

Shell commands with file patterns, pushd -n or dirs now need approval more often

The Bash safety check now refuses to auto-approve more commands, including unescaped * or ? patterns and pushd -n

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
Bash ToolArea: what it touches
ImprovementsKind: in v2.1.314,
ImprovementsSection of the release

Unclear It is not clear whether these stricter checks apply in every session or only under a particular shell mode.

What

Before approving a shell command automatically, Claude Code checks whether it is safe. That check is now stricter. It refuses:

  • words with * or ? that the shell would expand into a list of files, including where an even number of backslashes does not escape them
  • pushd -n, which puts a directory on the stack without entering it, so a later ~1 refers to it
  • dirs words that do the same

It also checks values passed to ssh dynamic options. Each case has its own refusal message. For pushd -n, the message suggests using pushd without -n, or cd.

Why

More commands will ask for your permission instead of running automatically.

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 clear whether these stricter checks apply in every session or only under a particular shell mode.

See this entry in the whole of v2.1.314 →

Feedback