{"version":"2.1.287","anchor":"xargs-permission-reason-reworded","canonical_anchor":"xargs-permission-reason-reworded","heading":"Plainer reason shown when xargs feeds input to find or jq","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/xargs-permission-reason-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plainer reason shown when xargs feeds input to find or jq\n\nThe permission reason for xargs passing its input to find or jq now says in plain words what xargs does\n\n**What**\n\nWhen Claude wants to run a command where `xargs` passes arguments to `find` or `jq`, Claude Code asks you for permission and gives a reason. That reason has been reworded. It now explains that xargs adds arguments it reads from its input to the command. Before, it said that \"stdin-appended arguments cannot be statically analyzed\".\n\n**Why**\n\nThe new wording is easier to understand when you are deciding whether to allow the command.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}