Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

xargs

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

A broader detector for destructive shell commands exists, but nothing visibly uses its verdict.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.242.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 161on this box, as of v2.1.322
Written about v2.1.242 first named in a changelog, 24 Aug 2026

In the changelogs

7

Releases whose published page names xargs.

  1. v2.1.315
    Bash safety checks now catch relative paths hidden behind variables

    The Bash safety check now treats more values as relative paths, so some commands that ran without asking will now ask first

    found in this entry's text

  2. v2.1.314
    Stricter safety checks for find, rg, sort, read, xargs and awk commands

    Claude Code checks more shell commands more strictly before running them without asking, so some will now ask for permission

    found in this entry's text

  3. v2.1.287
    Clearer wording when Claude Code cannot check an awk or xargs command

    Permission messages for awk and xargs commands now say plainly that what the command will run cannot be checked in advance

    found in this entry's text

  4. v2.1.287
    Plainer reason shown when xargs feeds input to find or jq

    The permission reason for xargs passing its input to find or jq now says in plain words what xargs does

    found in this entry's text

  5. v2.1.268
    New bash-command taxonomy for telemetry

    Claude Code now classifies every bash command you run for internal telemetry

    found in this entry's text

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

    named in this entry, found in this entry's text

  7. v2.1.242
    A broader classifier for destructive shell commands

    A broader detector for destructive shell commands exists, but nothing visibly uses its verdict.

    found in this entry's text

First cited

0

No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback