{"version":"2.1.288","anchor":"bash-parser-records-hasloop-awk-rejection-reason-shortened","canonical_anchor":"bash-parser-records-hasloop-awk-rejection-reason-shortened","heading":"Shorter reason shown when an awk command cannot be checked in advance","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/bash-parser-records-hasloop-awk-rejection-reason-shortened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Shorter reason shown when an awk command cannot be checked in advance\n\nThe reason Claude Code gives for not treating an awk command as safe is shorter and no longer mentions an option hiding its program\n\n**Unclear.** What Claude Code does with the new record of whether a command contains a loop is not known.\n\n**What**\n\nClaude Code checks some shell commands before running them to decide whether they are safe to run without asking you. When an `awk` command uses an option that stops Claude Code from seeing what it will run, the reason shown is now shorter. It no longer says that the option can hide the program.\n\nThe part of Claude Code that reads shell commands also now records whether a command contains a loop.\n\n**Why**\n\nYou may see this reworded reason in permission prompts, the questions Claude Code asks before running a command, when Claude wants to run such an `awk` command.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}