{"version":"2.1.309","anchor":"bash-safety-parser-rejects-more-shell-forms","canonical_anchor":"bash-safety-parser-rejects-more-shell-forms","heading":"More shell commands now need your approval before running","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/bash-safety-parser-rejects-more-shell-forms","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### More shell commands now need your approval before running\n\nClaude Code's Bash safety check now rejects more shell forms, including some patterns, some here-documents and some locale settings, so more commands prompt\n\n**What**\n\nClaude Code reads each shell command to decide whether it is safe to run without asking you. It now rejects more kinds of command, and these will ask for permission:\n\n- brace expressions, extended glob patterns and regular expressions that still contain unexpanded patterns\n\n- here-documents, meaning blocks of text passed into a command, whose body zsh would expand differently\n\n- a locale setting taken from a path the command chooses\n\n- `LC_*` locale values that Claude Code cannot check\n\nThe check on locale settings from a path is controlled by a setting Claude Code reads from the server.\n\n**Why**\n\nMore commands will stop and ask you instead of running on their own. This closes gaps where the shell might run something different from what Claude Code thought it would.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}