tengu_lantern_sconce_copy
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.277, including the newest one read.
Usage-limit banner wording can now be overridden remotely instead of being fixed text
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.277.
In the changelogs
3Releases whose published page names tengu_lantern_sconce_copy.
-
v2.1.284
VS Code extension refreshes all its feature switches when policy changes
When the product-feedback policy changes, Claude Code now re-sends every feature switch to the VS Code extension, not just two of them
gate cited by this entry
-
v2.1.277
Usage-limit banner text can be overridden from remote config
Usage-limit banner wording can now be overridden remotely instead of being fixed text
gate cited by this entry
-
v2.1.277
Usage-limit warning message reworked with remote-configurable copy and added link
Usage-limit warning now uses remote-managed text and links to clau.de/wrap-up
gate cited by this entry
Gate readings
2| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.284 read on another version | Not enough to say | no value returned | no value returned | not a boolean we can read |
| v2.1.277 read on another version | Not enough to say | no value returned | no value returned | not a boolean we can read |
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
5| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | {"credits_on":"Usage limit reached · continuing to work, then switching to usage credits"} | 2026-10-17T05:30:04Z | 2026-11-06T13:45:04Z | v2.1.302 to v2.1.318 |
| this account | {"credits_on":"Usage limit reached · continuing to work, then switching to usage credits"} | 2026-09-23T08:10:07Z | 2026-11-06T13:45:04Z | v2.1.280 to v2.1.318 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | {"credits_on":"Usage limit reached · continuing to work, then switching to usage credits"} | 2026-09-23T08:05:05Z | 2026-10-17T05:10:04Z | v2.1.280 to v2.1.302 |
| anonymous | [] | 2026-09-23T07:55:05Z | 2026-09-23T07:55:05Z | v2.1.280 |
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_lantern_sconce_copy 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.
Presence across releases
1Build by build
39One 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.