{"version":"2.1.299","anchor":"awk-programs-with-pipes-to-commands-are-refused-by-the-bash","canonical_anchor":"awk-programs-with-pipes-to-commands-are-refused-by-the-bash","heading":"Awk commands that pipe to other programs are no longer auto-approved","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/awk-programs-with-pipes-to-commands-are-refused-by-the-bash","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Awk commands that pipe to other programs are no longer auto-approved\n\nAn awk program that pipes output to a command, or reads from one, is no longer treated as safe to run without asking\n\n**What**\n\nawk is a text-processing command. Claude Code checks shell commands to decide which are safe to run without asking you. An awk program now counts as unsafe when it has a `|` after `print` or `printf`, or before `getline`, because awk can use those to run another command. Previously only a few other awk forms were refused.\n\n**Why**\n\nThis closes a gap where an awk command could run other programs while being approved automatically.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}