{"version":"2.1.293","anchor":"plan-limits-end-date-check-replaced-by-clearing-ask-class","canonical_anchor":"plan-limits-end-date-check-replaced-by-clearing-ask-class","heading":"Internal plan limit check reworked","tier":"internal","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/plan-limits-end-date-check-replaced-by-clearing-ask-class","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Internal plan limit check reworked\n\nA step that used to check whether a plan limit period had ended now resets other internal tracking instead\n\n**Unclear.** It is not clear whether this changes when plan limits apply or show up for users.\n\n**What**\n\nClaude Code used to have a step that checked whether the end date of a plan limit had passed. That step no longer looks at the date. It now clears some internal records Claude Code keeps about pending requests. Claude Code also tracks running routines in a new record, which is emptied when its state resets.\n\n**Why**\n\nThis is a change to how Claude Code keeps track of plan limits and routines behind the scenes.\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}