{"version":"2.1.236","anchor":"visible-notice-when-approaching-the-5-hour-usage-limit","canonical_anchor":"visible-notice-when-approaching-the-5-hour-usage-limit","heading":"Visible notice when approaching the 5-hour usage limit","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/visible-notice-when-approaching-the-5-hour-usage-limit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Visible notice when approaching the 5-hour usage limit\n\nYou could be told when you are near the 5-hour usage limit instead of Claude just wrapping up.\n\n**What**\n\nA user-facing message, \"Approaching your 5-hour usage limit \u2014 Claude will wrap up the current step.\", is shown before the existing wrap-up instruction is injected, so the behaviour is explained rather than silent. It is behind the `tengu_vellum_anchor` flag, which falls back to false, so it is off in this build unless remote config enables it.\n\n**Evidence**\n\n`Approaching your 5-hour usage limit \u2014 Claude will wrap up the current step.`\n\n- Flag `tengu_vellum_anchor`: Off in both readings (read for one account on one subscription tier against v2.1.236; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}