The usage-limit grace notice runs only when tengu_lantern_sconce returns true, and the compiled value is false.
A new status bar item can show Usage limit reached with the time it resets, or Usage limit reached · a little extra on us, then your credits when extra usage is being covered for you. It runs only when the server flag tengu_lantern_sconce returns true; the value compiled into this build is false, so nothing appears unless a server says otherwise.
- The notice has three internal phases: finishing the current work, covered by extra usage, and waiting for the reset.
- It emits a
usage_limit_grace_noticeevent when shown. - A separate mock path can force the notice on for testing regardless of the flag.
Usage limit reached \xB7 a little extra on us, then your credits
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_lantern_sconce Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.247: off
Read once, for one account on one subscription tier, against v2.1.247. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: tengu_lantern_sconce