Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.304 ·

Idle features now wait while you are past a usage limit

Idle hints and the idle-cache quota now follow pastUsageLimitUntil, and a model_requires_usage_credits error gets new handling

Group of 2 You'll notice Improvements
JSON All of v2.1.304
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
ImprovementsKind: in v2.1.304,
ImprovementsSection of the release

What

Claude 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:

  • 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.
  • 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.
  • 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.

Why

In 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.

See this entry in the whole of v2.1.304 →

Feedback