{"version":"2.1.319","anchor":"stricter-bash-permission-checks-for-pipes-and-git-push-o","canonical_anchor":"stricter-bash-permission-checks-for-pipes-and-git-push-o","heading":"Stricter permission checks for Bash commands with pipes and for git push -o","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/stricter-bash-permission-checks-for-pipes-and-git-push-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Stricter permission checks for Bash commands with pipes and for git push -o\n\nBash commands with a pipe now get the same extra permission check as those with $, and git push -o is covered by push rules\n\n**Unclear.** Which commands have their PowerShell rule forms skipped is not stated.\n\n**What**\n\nClaude Code checks each Bash command against your permission rules. Three changes:\n\n- An extra check that used to run only for commands containing `$` now also runs for commands containing `|`, the pipe that sends one command's output to another\n\n- `git push -o`, which sends push options, is now included in the git push patterns\n\n- For some commands, the PowerShell forms of a rule are skipped\n\n**Why**\n\nMore commands with pipes now go through closer permission checks, so fewer are approved automatically.\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"}