{"version":"2.1.283","anchor":"bash-read-onlysafety-check-now-covers-more-command-shapes","canonical_anchor":"bash-read-onlysafety-check-now-covers-more-command-shapes","heading":"Safety check for combined shell commands has changed","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/bash-read-onlysafety-check-now-covers-more-command-shapes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Safety check for combined shell commands has changed\n\nClaude Code's check on shell commands joined together now inspects two lists of commands at once and looks at different lists for output redirects\n\n**Unclear.** What the new check tests for, and so which commands are treated differently, is not known.\n\n**What**\n\nWhen you or Claude run several shell commands joined into one line, Claude Code checks them to decide whether they are safe or read-only. That check now runs over two lists of commands together rather than checking each command on its own. The part that looks for redirects, where output is sent to a file, now looks at different lists than before.\n\n**Why**\n\nThis may change which shell commands are approved without asking you and which ones are flagged.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}