Usage-limit messages can append "progress saved", but callers only pass it when a server flag is on.
A ' · progress saved' suffix on usage-limit messages is only passed when a remote setting that falls back to off is on.
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: on
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
What's wrong with this entry?
The code that writes "You've hit your …" and "You're out of usage credits…" can now append " · progress saved" to those messages. It is off in this build: callers only pass the flag when the tengu_vellum_anchor remote setting is on, which falls back to off, so the messages read exactly as before.
- The suffix is a new option on the message builder rather than a separate string, so both limit messages pick it up together.
progressSavedSuffix
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.234
Rate-limit prompts resolve model aliases to the model that actually answers
Both mention rate limit
-
v2.1.234
Quota rejections feed a new auto-resume controller
Both mention rate limit
-
v2.1.239
Spend and rate limit notices say when the limit resets
Both mention rate limit