tengu_steady_plum
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 effort-downgrade nudge now works per model instead of just one, but each model needs its own flag turned on.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.263.
In the changelogs
4Releases whose published page names tengu_steady_plum.
-
v2.1.263
Effort-medium nudge generalized to multiple models and effort levels
The effort-downgrade nudge now works per model instead of just one, but each model needs its own flag turned on.
gate cited by this entry
-
v2.1.263
Effort-medium nudge generalized to per-model remote-config gates
The effort-downgrade nudge was rebuilt to support multiple models, each hidden behind its own remote switch.
gate cited by this entry, found in this entry's text
-
v2.1.263
Effort-medium-nudge remote config now validated for effort-level ordering, plus fromEffort/toEffort treated as invalid fields
Server-served effort nudge text is now rejected outright if its effort-level ordering looks invalid.
gate cited by this entry
-
v2.1.263
Effort nudge confirm dialog supports templated copy and an optional warning banner
The effort nudge dialog can now fill in the model and levels by name and show a warning banner, once enabled.
gate cited by this entry
Gate readings
0No 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.
Flag server, over time
8| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | [] | 2026-10-17T05:30:04Z | 2026-11-12T05:45:09Z | v2.1.302 to v2.1.322 |
| this account | [] | 2026-09-10T21:47:12Z | 2026-11-12T05:45:09Z | v2.1.268 to v2.1.322 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | [] | 2026-09-06T04:10:04Z | 2026-10-17T05:10:04Z | v2.1.263 to v2.1.302 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | [] | 2026-09-08T20:36:15Z | 2026-09-10T17:40:05Z | v2.1.263 to v2.1.267 |
| this account | no longer carried | 2026-09-08T20:34:58Z | 2026-09-08T20:34:58Z | v2.1.265 |
| this account | [] | 2026-09-06T04:35:03Z | 2026-09-08T18:45:05Z | v2.1.263 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
0No 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
0The 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.