The token countdown reminder budget is read once at start, so mid-session config changes are ignored.
tengu_lapis_anchor 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.232: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
tengu_lapis_anchor_budget 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.232: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.232. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The starting budget for the padded token countdown reminder is now read once and cached for the session rather than watched for changes, so a remote config update mid-session no longer takes effect. The reminder itself is off by default behind tengu_lapis_anchor.
- Resolution order is unchanged: the
CLAUDE_CODE_TOTAL_TOKENS_REMINDER_BUDGETenvironment variable, then the matching settings key, then thetengu_lapis_anchor_budgetremote value.
totalTokensReminderBudget
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.