tengu_quiet_lantern
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.278, including the newest one read.
A new gate, tengu_quiet_lantern, controls whether the server classifier falls back to local when unsupported
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.278.
In the changelogs
3Releases whose published page names tengu_quiet_lantern.
-
v2.1.278
New gate tengu_quiet_lantern controls arbiter local-fallback triggers
A new gate, tengu_quiet_lantern, controls whether the server classifier falls back to local when unsupported
named in this entry, gate cited by this entry, found in this entry's text
-
v2.1.278
'Auto mode server' status row added to the model/context panel
The model/context status panel gains an 'Auto mode server' row showing Enabled or Disabled
named in this entry, gate cited by this entry
-
v2.1.278
Third-party server classifier gating tightened
Auto mode's server-classifier eligibility check adds a new exclusion and respects CLAUDE_CODE_AUTO_MODE_SERVER as an override
gate cited by this entry
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.278 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.
Flag server, over time
4| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-06T10:30:06Z | v2.1.302 to v2.1.318 |
| this account | on | 2026-10-01T00:50:05Z | 2026-11-06T10:30:06Z | v2.1.286 to v2.1.318 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-10-01T00:40:04Z | 2026-10-17T05:10:04Z | v2.1.286 to v2.1.302 |
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
1The earliest release whose published evidence quoted tengu_quiet_lantern was v2.1.278, 19 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.
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.