Claude could be nudged to wrap up or checkpoint during your usage-limit grace window, but nothing fires.
A grace-window wrap-up nudge has off, wrap-up and next-steps modes, resolving to off with no server value.
tengu_lantern_wick_mode 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.227: 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.227. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When you are inside the usage-limit grace window, Claude Code can insert a hidden message asking the model either to wrap up, or to checkpoint and list up to three remaining pieces of work. The behaviour comes from tengu_lantern_wick_mode, which resolves to off, wrap-up or next-steps; with no remote value it is off, so nothing is injected in this build.
tengu_lantern_wick_mode
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