{"version":"2.1.273","anchor":"differential-testing-detector-now-flags-glued-subshell-group","canonical_anchor":"differential-testing-detector-now-flags-glued-subshell-group","heading":"Differential-testing detector now flags glued subshell groups too","tier":"notice","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/differential-testing-detector-now-flags-glued-subshell-group","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Differential-testing detector now flags glued subshell groups too\n\nClaude Code's bash\/zsh compatibility checker now flags parentheses glued directly onto a preceding word as a shell-specific risk\n\n**What**\n\nClaude Code's detector for shell commands that might behave differently across bash and zsh has a new case: a `(...)` group that appears directly attached to the end of a preceding word or statement, on the same line. Bash rejects this kind of command outright, but zsh instead reads the glued parentheses as a glob-group word and expands whatever follows it. Previously, this specific pattern only triggered a generic 'statement follows statement' message.\n\n**Why**\n\nThis gives a clearer, more specific warning for a command shape where bash and zsh genuinely diverge in behavior, instead of a generic catch-all message.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}