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.
This tightens the safety checks Claude Code runs on bash commands before executing them, catching more shell syntax that could behave unexpectedly.
tengu_shimmying_mochi Not enough to sayNothing 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
New in this build: tengu_shimmying_mochi