A usage-limits surface for Pro and Max accounts is now hidden behind an off flag.
tengu_ember_latch falls back to off, hiding a surface that previously showed.
tengu_ember_latch Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.248: on
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A limits-related interface that previously showed for Pro and Max accounts is now wrapped in an additional check tied to the tengu_ember_latch feature flag. Nothing in this build sets that flag, and it falls back to off, so the surface stays hidden unless server config enables it.
- The Pro/Max account condition still applies underneath the new outer check.
tengu_ember_latch
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit