Token-reminder settings can now arrive from the server, but your env var and setting still win.
What's wrong with this entry?
The three settings behind the total-tokens reminder (its mode, its budget, and whether it appears after your turn) are read first from a configuration blob the server sends, and only fall back to the feature-flag defaults "padded-countdown", the default budget and on. The CLAUDE_CODE_TOTAL_TOKENS_REMINDER environment variable and the totalTokensReminder settings key still override both.
- When a server-provided value is used, it is reported as
tengu_lapis_anchor_from_client_data. - A server value of the wrong type logs a warning and falls back to the flag default rather than failing.
falling through to GrowthBook
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.248
Token reminder budget override now takes effect
Both mention total token reminder context
- v2.1.232 Token-countdown reminder budget fixed at session start
- v2.1.233 Remaining-token countdown is now on by default