{"version":"2.1.304","anchor":"idle-hint-scheduler-defers-while-past-a-usage-limit","canonical_anchor":"idle-hint-scheduler-defers-while-past-a-usage-limit","heading":"Idle features now wait while you are past a usage limit","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/idle-hint-scheduler-defers-while-past-a-usage-limit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Idle features now wait while you are past a usage limit\n\nIdle hints and the idle-cache quota now follow pastUsageLimitUntil, and a model_requires_usage_credits error gets new handling\n\n**What**\n\nClaude Code now checks how long your account is past its usage limit, through a value called `pastUsageLimitUntil`. A usage limit is the cap on how much you can use Claude in a period of time. Several things that run while you are idle now take that value into account:\n\n- The idle-hint scheduler is the part that decides when to show a hint while you are not typing. It now asks `pastUsageLimitUntil()` first. If you are past a limit, it skips the hint and schedules its next check for the time the limit ends. If that time is not a usable number, it uses a fallback delay instead.\n\n- The controller that manages quota for the idle cache now receives `pastUsageLimitUntil` as an input. Quota here means how much of your allowance that work may use.\n\n- An error from the assistant named `model_requires_usage_credits` now triggers two new handlers, so the interface reacts when a model needs usage credits.\n\n**Why**\n\nIn practice, idle hints no longer fire while you are rate limited, and idle background work is aware of when your limit ends. You also get a response from the interface when you pick a model that requires usage credits, rather than a bare error.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}