tengu_iridescent_boot
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.281, including the newest one read.
rm -r on a path made entirely of $(...) or backtick output now always asks, and permission rules cannot auto-allow it
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.281.
In the changelogs
8Releases whose published page names tengu_iridescent_boot.
-
v2.1.321
Shell permission checks now cover more cp, mv and rm cases
Claude Code now checks where cp and mv really write, looks inside ${HOME} in rm targets, and lets deny rules override rm checks
gate cited by this entry
-
v2.1.319
Stricter shell permission checks for rm and Windows paths
Claude Code now asks before an rm on a Windows path it cannot place, and checks nested commands and auto mode commands more closely
gate cited by this entry
-
v2.1.305
Approval prompt for
rmon a command's output now checks more of the commandThe approval check for a recursive
rmaimed at a command's output now also looks at extra parts of the commandgate cited by this entry
-
v2.1.304
rmon a mounted drive or a drive's top level now needs your approvalClaude Code now asks before
rmremoves a mounted drive, its parent folder or a top-level item on a drive; an environment variable turns this offgate cited by this entry
-
v2.1.290
Some
rmcommands with variables set in front now ask firstClaude Code now rechecks
rmcommands with variables set before a declaration, and asks you when it cannot check them allgate cited by this entry
-
v2.1.288
Bash permission checks now look inside shell code passed to other shells
Before running a Bash command, Claude Code now also checks shell scripts written inline in it, such as heredocs or code passed with -c
gate cited by this entry
-
v2.1.281
rm -r on command-substitution output now always prompts (tengu_iridescent_boot, CLAUDE_CODE_DISABLE_SUBSTITUTION_RM_PROMPT)
rm -ron a path made entirely of$(...)or backtick output now always asks, and permission rules cannot auto-allow itgate cited by this entry, found in this entry's text
-
v2.1.281
rm -r on a command-substitution target now always asks, unless an env var or flag turns it off
A recursive rm aimed at the output of a command substitution now always asks you first, and permission rules cannot auto-allow it
gate cited by this entry, found in this entry's text
Gate readings
7| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.321 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.319 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.305 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.304 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.290 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.288 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.281 read on another version | Not enough to say | no value returned | no value returned | on |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
First cited
1The earliest release whose published evidence quoted tengu_iridescent_boot was v2.1.305, 20 Oct 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.
Presence across releases
1Build by build
38One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
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.