{"version":"2.1.271","anchor":"bash-tool-static-command-analysis-now-tracks-per-argument-un","canonical_anchor":"bash-tool-static-command-analysis-now-tracks-per-argument-un","heading":"Bash-tool static command analysis now tracks per-argument unquoted-glob status","tier":"internal","area":"Bash Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/bash-tool-static-command-analysis-now-tracks-per-argument-un","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Bash-tool static command analysis now tracks per-argument unquoted-glob status\n\nClaude Code's shell command analysis now flags which specific arguments contain unquoted glob patterns\n\n**What**\n\nWhen Claude Code statically analyzes a bash command (before running it, to check its safety), it now records, for each individual argument, whether that argument contained an unquoted glob pattern (a wildcard like `*` that wasn't wrapped in quotes). This is returned as a new `argvUnquotedGlob` field alongside the parsed argument list for straightforward (\"simple\") commands.\n\n**Why**\n\nUnquoted globs can expand unexpectedly and cause a command to affect more files than intended. Tracking this per-argument gives Claude Code finer-grained information to reason about whether a command is safe to run.\n\n- Area: Bash Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}