{"version":"2.1.287","anchor":"bash-permission-check-reasons-reworded-for-awk-and-xargs","canonical_anchor":"bash-permission-check-reasons-reworded-for-awk-and-xargs","heading":"Clearer wording when Claude Code cannot check an awk or xargs command","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/bash-permission-check-reasons-reworded-for-awk-and-xargs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Clearer wording when Claude Code cannot check an awk or xargs command\n\nPermission messages for awk and xargs commands now say plainly that what the command will run cannot be checked in advance\n\n**What**\n\nBefore running a shell command, Claude Code tries to work out what it will do so it can decide whether to ask you for permission. For some `awk` and `xargs` commands that is not possible, and Claude Code shows a reason. Those reasons have been reworded to say that what the command will run \"cannot be checked in advance\". For example: \"awk is given an option that can hide its program, so what it will run cannot be checked in advance\". When these messages appear has not changed.\n\n**Why**\n\nThe permission prompt now explains in plain words why it is asking.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}