Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Rate-limit tracker can now register and signal usage-limit waits

The rate-limit tracker gained a usage-limit-wait set and events so callers can register that they're waiting and be notified when that changes

Group of 2 Under the hood Internal Changes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Rate LimitsArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release

What

The internal rate-limit/subscription tracker gained a new way to track callers that are waiting on a usage limit:

  • A usageLimitWaits set and a usageLimitWaitsChanged event were added alongside the existing statusChanged, overageInUse, and quotaRejected signals, plus a helper that snapshots the current waiters as an array.
  • A public beginUsageLimitWait(e) method (and emitUsageLimitWaitsChanged) lets a caller register itself as waiting on a usage limit and be notified whenever the set of waiters changes.

Why

This lets other parts of Claude Code know, in real time, when something is blocked waiting on a usage limit, so they can react (for example, showing a status message) instead of the wait being invisible.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding doesn't say what visibly changes for a user as a result of this tracking.

See this entry in the whole of v2.1.280 →

Feedback