Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.257 ·

xargs commands can now qualify as read-only

An xargs call wrapping echo, printf or wc can now count as read-only instead of prompting.

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaPermissionswhat it touches
KindImprovementsin v2.1.257,
You'll notice

An xargs call wrapping echo, printf or wc can now count as read-only instead of prompting.

The 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.

Read from
Names in the bundlexargs
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up xargs, on All settings. * A command starting with `sudo`, `eval`, or `xargs` settings-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up xargs, on All settings.

See this entry in the whole of v2.1.257 →

Feedback