Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.274 ·

Bash parameter-expansion safety checks tightened, gated by tengu_shimmying_mochi

Claude Code's bash-safety checker now rejects more risky variable-expansion patterns

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaBash Safetywhat it touches
KindImprovementsin v2.1.274,
You'll notice No documentation found

Claude Code's bash-safety checker now rejects more risky variable-expansion patterns

What

The analyzer that judges whether a shell command's variable expansions are safe or need extra scrutiny now refuses two more patterns: ${!...} forms used for name-listing or positional parameters, and ${ |...} patterns. It also added a stricter "canonical form" check, requiring that the parsed pieces of an expansion reconstruct the original text exactly before it's treated as safe.

Why

This tightens the safety checks Claude Code runs on bash commands before executing them, catching more shell syntax that could behave unexpectedly.

Read from
Names in the bundletengu_shimmying_mochi
Feature flag
tengu_shimmying_mochi 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.274: on

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.274. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_shimmying_mochi

See this entry in the whole of v2.1.274 →

Feedback