{"version":"2.1.273","anchor":"bash-subshellcd-checks-new-content-scan-for-unparsed-comma","canonical_anchor":"bash-subshellcd-checks-new-content-scan-for-unparsed-comma","heading":"Bash subshell\/cd checks: new content scan for unparsed command substitutions","tier":"notice","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/bash-subshellcd-checks-new-content-scan-for-unparsed-comma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bash subshell\/cd checks: new content scan for unparsed command substitutions\n\nBash cd checks now scan command substitutions inside unparsed subshells for risky commands like rm\n\n**What**\n\nWhen Claude Code can't fully analyze a bash subshell (an 'unparsed command substitution') that also contains a `cd`, it now separately scans the command and process substitutions inside it, looking for risky commands such as `rm` or `rmdir` hidden within them. If there are more than 64 such substitutions to check, Claude Code now denies the command outright with the message 'too many command substitutions to analyze', rather than trying to analyze all of them.\n\n**Why**\n\nThis closes a gap where a destructive command like `rm` could be tucked inside a subshell that changes directory, and it makes Claude Code refuse rather than guess when there's too much nested substitution to safely check.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}