You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Bash SafetyArea: what it touches
ImprovementsKind: in v2.1.309,
ImprovementsSection of the release
Unclear Whether a command that cannot be parsed always leads to a permission prompt is not confirmed.
What
Before running a shell command, Claude Code reads its structure to check it against your permission rules. It now marks a command as one it could not parse when it contains any of these:
a $ or a backtick inside a double-quoted part of a string, including inside an ANSI-C string written as $'...'
a backslash followed by a line break inside an expansion
$[
${ followed by a space or |
Before, $'...' strings were scanned without this check for nested expansions. Claude Code also now recognises a list of read-only shell variable names, such as BASHPID and BASH_SOURCE.
Why
Commands written with this kind of quoting now land in the could-not-parse case, which is where Claude Code tends to ask for permission rather than rely on a rule.
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 doubtWhether a command that cannot be parsed always leads to a permission prompt is not confirmed.
