Unclear How the new wildcard check is used in permission decisions is not known.
What
Claude Code reads shell commands before running them so it can check permissions. Two things changed in that reading:
- A new check spots wildcard patterns, such as
*.txt. Plain words and numbers count as wildcards when they contain*,?or[. Quoted strings and variable expansions do not. Any other part of a command is treated as possibly a wildcard. - A command substitution is a command written inside another command, such as
$(...). When these are nested too deeply, the error now reads "command substitutions nested too deeply".
Why
These changes sit in the code that decides whether a shell command needs your permission, so those checks may become stricter.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
How the new wildcard check is used in permission decisions is not known.