{"version":"2.1.290","anchor":"bash-analyzer-flags-declaration-commands-with-quote-scan-des","canonical_anchor":"bash-analyzer-flags-declaration-commands-with-quote-scan-des","heading":"Shell command safety check notes a quoting risk in declarations","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bash-analyzer-flags-declaration-commands-with-quote-scan-des","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shell command safety check notes a quoting risk in declarations\n\nClaude Code's shell command analysis now marks declaration commands where its quote tracking may go out of step\n\n**Unclear.** It is not clear where this new marker is used or what it changes about prompts.\n\n**What**\n\nBefore running a shell command, Claude Code analyses it to decide whether to ask your permission. For declaration commands (commands such as `declare` or `export` that set variables), the result of that analysis now records whether the way Claude Code tracks quotes might go out of step with the real command.\n\n**Why**\n\nThis tightens the safety check on shell commands, so that a confusing quoting pattern is less likely to slip through without a prompt.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}