Claude now gets a running count of tokens left by default, re-anchored on each of your prompts.
tengu_lapis_anchor_user_turn Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.233: off
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.233. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Claude Code emits a <total_tokens>N tokens left</total_tokens> block in the system prompt and after each tool result, counting down from the configured budget. This used to be off unless enabled; the built-in fallback is now padded-countdown. The companion behaviour of re-anchoring the countdown on each regular user prompt also flipped to on by default. Both can still be set explicitly, and remote config can override either.
- Resolution order: env var
CLAUDE_CODE_TOTAL_TOKENS_REMINDER, then thetotalTokensRemindersetting, then the server-side value whose in-source fallback moved from "off" to "padded-countdown". - The budget comes from
totalTokensReminderBudget. - Re-anchoring uses
CLAUDE_CODE_TOTAL_TOKENS_REMINDER_AFTER_USER_TURN, thentotalTokensReminderAfterUserTurn, then the server value whose fallback flipped from false to true. - Suppressed entirely by
CLAUDE_CODE_DISABLE_ATTACHMENTSorCLAUDE_CODE_SIMPLE. - The source only fixes the fallback; a server-side value still wins.
is on \u2014 task-budget semantics). Defaults to padded-countdown. , "@internal Emit a <total_tokens>N tokens left</total_tokens> block in the system prompt, after each tool result, tengu_lapis_anchor_user_turn
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.224
Attention budget: state and telemetry land, nothing can trigger it
Both mention context management
-
v2.1.234
Background-event polling no longer piles up reminder text
Both mention context management
-
v2.1.232
Worker processes no longer inherit resume state
Both mention management