{"version":"2.1.229","anchor":"wrap-up-hint-when-you-are-close-to-the-usage-limit","canonical_anchor":"wrap-up-hint-when-you-are-close-to-the-usage-limit","heading":"Wrap-up hint when you are close to the usage limit","tier":"soon","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/wrap-up-hint-when-you-are-close-to-the-usage-limit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Wrap-up hint when you are close to the usage limit\n\nPast 95% of five-hour usage Claude could be told to checkpoint and list remaining work, off here.\n\n**What**\n\nWhen five-hour usage crosses 95% and the account is not in overage, Claude gets a message telling it to checkpoint: finish the current step, list up to three bullets of the most impactful remaining work, and start no subagents or long-running work. A `usage_limit_near_wrapup` event is recorded. The whole path is behind the `tengu_vellum_anchor` gate, which falls back to off, so with no remote config value nothing is injected.\n\n**Details**\n\n- The exact injected text is \"[Usage limit approaching. Checkpoint now: finish the current step, then list up to 3 short bullets of the most impactful remaining work. Don't start subagents or long-running work.]\".\n- None of this machinery existed in 2.1.228.\n\n**Evidence**\n\n`tengu_vellum_anchor`\n\n- Flag `tengu_vellum_anchor`: Off in both readings (read for one account on one subscription tier against v2.1.229; this account: off, anonymous baseline: off, compiled default: off) 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: 4\/5\n- Present in the build but not switched on"}