Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

tengu_bash_dangerous_rm_too_complex

flag never mined JSON

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

The dangerous-rm safety check for bash commands can now be extended with an extra custom check

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

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 159on this box, as of v2.1.319
Written about v2.1.273 first named in a changelog, 15 Sep 2026

In the changelogs

3

Releases whose published page names tengu_bash_dangerous_rm_too_complex.

  1. v2.1.281
    Bash rm check now flags rm targets built from variables that may be empty (tengu_bright_lake, falls back to on)

    The Bash rm check now follows shell variables and asks for approval when an empty one could make a path reach /

    found in this entry's text

  2. v2.1.277
    Write tool's dangerous-rm-on-unset-variable check refactored, message likely unchanged

    Internal cleanup of the dangerous rm-with-unset-variable safety check, no visible behavior change

    found in this entry's text

  3. v2.1.273
    Dangerous-rm check gains a pluggable extra-deny hook

    The dangerous-rm safety check for bash commands can now be extended with an extra custom check

    gate cited by this entry

Gate readings

0

No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.

First cited

1

The earliest release whose published evidence quoted tengu_bash_dangerous_rm_too_complex was v2.1.277, 18 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.27718 Sep 2026tengu_bash_dangerous_rm_too_complex

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 feature flag does. All feature flags.

Feedback