You could be told when you are near the 5-hour usage limit instead of Claude just wrapping up.
The approaching-limit notice is behind tengu_vellum_anchor, which falls back to false.
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.236: on
Read once, for one account on one subscription tier, against v2.1.236. 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 user-facing message, "Approaching your 5-hour usage limit — Claude will wrap up the current step.", is shown before the existing wrap-up instruction is injected, so the behaviour is explained rather than silent. It is behind the tengu_vellum_anchor flag, which falls back to false, so it is off in this build unless remote config enables it.
Approaching your 5-hour usage limit — Claude will wrap up the current step.
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.239
Requests can now be marked as running against a slow usage budget
Both mention usage limit
-
v2.1.239
A low-priority choice is wired into the usage-limit menu
Both mention usage limit
-
v2.1.242
Clearer lower-priority mode messages
Both mention usage limit