The grace-window nudge can now ask Claude to checkpoint and list remaining work, but stays off.
A next-steps grace-window mode exists alongside wrap-up, with off as the fallback.
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 hit a usage limit and a grace window opens, the wrap-up nudge is no longer a single fixed message. It is now a three-way mode set by tengu_lantern_wick_mode: off, wrap-up, or the new next-steps, which asks the model to checkpoint and list up to 3 bullets of remaining work. The fallback is off, and any unrecognised value is treated as off, so nothing appears unless the server turns it on.
- The message opens "[Usage limit reached — grace window active. Checkpoint now: finish the ...".
- The telemetry event now records which variant fired, including
next_steps.
[Usage limit reached \u2014 grace window active. Checkpoint now: finish the
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