{"version":"2.1.227","anchor":"usage-limit-grace-window-can-ask-for-next-steps","canonical_anchor":"usage-limit-grace-window-can-ask-for-next-steps","heading":"Usage-limit grace window can ask for next steps","tier":"soon","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/usage-limit-grace-window-can-ask-for-next-steps","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Usage-limit grace window can ask for next steps\n\nThe grace-window nudge can now ask Claude to checkpoint and list remaining work, but stays off.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The message opens \"[Usage limit reached \u2014 grace window active. Checkpoint now: finish the ...\".\n- The telemetry event now records which variant fired, including `next_steps`.\n\n**Evidence**\n\n`[Usage limit reached \\u2014 grace window active. Checkpoint now: finish the `\n\n- Flag `tengu_lantern_wick_mode`: Not enough to say (read for one account on one subscription tier against v2.1.227; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Rate Limits\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}