{"version":"2.1.290","anchor":"glob-character-detection-helper-and-shell-parser-changes","canonical_anchor":"glob-character-detection-helper-and-shell-parser-changes","heading":"Shell command parsing gains wildcard detection and a reworded nesting error","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/glob-character-detection-helper-and-shell-parser-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shell command parsing gains wildcard detection and a reworded nesting error\n\nClaude Code's shell command parser can now spot wildcard patterns, and its error for deeply nested command substitutions is reworded\n\n**Unclear.** How the new wildcard check is used in permission decisions is not known.\n\n**What**\n\nClaude Code reads shell commands before running them so it can check permissions. Two things changed in that reading:\n\n- 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.\n\n- 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\".\n\n**Why**\n\nThese changes sit in the code that decides whether a shell command needs your permission, so those checks may become stricter.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}