{"version":"2.1.257","anchor":"xargs-commands-can-now-qualify-as-read-only","canonical_anchor":"xargs-commands-can-now-qualify-as-read-only","heading":"xargs commands can now qualify as read-only","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/xargs-commands-can-now-qualify-as-read-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### xargs commands can now qualify as read-only\n\nAn xargs call wrapping echo, printf or wc can now count as read-only instead of prompting.\n\nThe read-only-command classifier now recognizes safe `xargs` invocations, checking the `xargs` flags and a trailing list of safe commands (`echo`, `printf`, `wc`). An `xargs` call wrapping one of these allowed commands can now be treated as read-only instead of forcing an ask prompt.\n\n- Area: Permissions\n- Names: `xargs`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}