{"version":"2.1.273","anchor":"shell-safety-analyzer-new-subshell-and-array-literal-detect","canonical_anchor":"shell-safety-analyzer-new-subshell-and-array-literal-detect","heading":"Shell-safety analyzer: new subshell and array-literal detectors","tier":"notice","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/shell-safety-analyzer-new-subshell-and-array-literal-detect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Shell-safety analyzer: new subshell and array-literal detectors\n\nShell-safety checker gains new detectors for hidden subshells and array-literal syntax\n\n**What**\n\nClaude Code's bash safety checker gained two new internal helpers:\n\n- One recursively checks whether a command or variable assignment contains a nested subshell (a command run in its own sub-process, e.g. via parentheses).\n\n- Another walks a parsed command looking for `=(` array-literal syntax hidden inside words, regular expressions, or expansions, falling back to treating the command as unsafe by default if parsing fails or the input is too long.\n\n**Why**\n\nThese detectors help the safety checker catch commands that use subshells or array-literal syntax to do something other than what they appear to on the surface, before deciding whether a command is safe to auto-run.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}