tengu_lucid_bittern
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.319, including the newest one read.
Behaviour that followed one remote switch is now split: part of it moves to a new switch, and both stay off by default
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.319.
In the changelogs
1Releases whose published page names tengu_lucid_bittern.
-
v2.1.319
One remote switch has been split into two
Behaviour that followed one remote switch is now split: part of it moves to a new switch, and both stay off by default
gate cited by this entry, found in this entry's text
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.319 read on another version | Not enough to say | no value returned | no value returned | off |
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_lucid_bittern was v2.1.319, 6 Nov 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
1One 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.