{"version":"2.1.227","anchor":"wrap-up-nudge-during-the-rate-limit-grace-window","canonical_anchor":"wrap-up-nudge-during-the-rate-limit-grace-window","heading":"Wrap-up nudge during the rate-limit grace window","tier":"soon","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/wrap-up-nudge-during-the-rate-limit-grace-window","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Wrap-up nudge during the rate-limit grace window\n\nClaude could be nudged to wrap up or checkpoint during your usage-limit grace window, but nothing fires.\n\n**What**\n\nWhen 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.\n\n**Evidence**\n\n`tengu_lantern_wick_mode`\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"}