A wrap-up checkpoint message at 95% usage is behind a gate that falls back to off.
When five-hour usage crosses 95% and the account is not in overage, Claude gets a message telling it to checkpoint: finish the current step, list up to three bullets of the most impactful remaining work, and start no subagents or long-running work. A usage_limit_near_wrapup event is recorded. The whole path is behind the tengu_vellum_anchor gate, which falls back to off, so with no remote config value nothing is injected.
- The exact injected text is "[Usage limit approaching. Checkpoint now: finish the current step, then list up to 3 short bullets of the most impactful remaining work. Don't start subagents or long-running work.]".
- None of this machinery existed in 2.1.228.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_vellum_anchor 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.229: 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.229. 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.
New in this build: tengu_vellum_anchor