[FEATURE] Replace weekly usage cutoffs with Velocity usage measurement and progressive throttling

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Weekly usage cutoffs affect development decisions before the limit is reached. Professional developers approaching their limit may avoid starting complex refactoring or new development because they need to reserve capacity for emergency fixes.

A complete cutoff makes it difficult to commit to substantial work. Developers risk losing access midway through a change or having no capacity available when an urgent production issue arises. This discourages productive use of Claude Code even while allowance remains.

The problem is both the interruption when the limit is reached and the work developers choose not to start because that interruption is possible.

Proposed Solution

Replace the weekly reset cadence with what I propose calling a “Velocity” limit. This would provide a continuously replenishing usage allowance with progressive throttling.

Full-speed usage would consume the available allowance. Throttling could begin in the final 20% and increase progressively as usage reaches or exceeds the threshold. Users would retain access at a reduced processing rate while capacity replenishes, similar to cellular unlimited data plans.
The reduced rate should remain sufficient for meaningful development. Throttling should affect speed or request throughput while preserving the selected model, context capacity, and response quality.

Users could optionally purchase extended usage to restore full speed immediately. Those who stay within their subscription budget would continue working at reduced speed.

The “Velocity” limit could be offered as a benefit exclusive to higher subscription tiers, providing an incentive to upgrade through continuity of access.
The usage display should show available capacity, the current throttle level, and estimated recovery time.

Alternative Solutions

• Purchase extended usage. (This restores access but requires spending beyond the subscription.)
• Wait for the weekly reset. (This interrupts development and can delay urgent work.)
• Reserve allowance for emergencies. (This discourages developers from starting substantial work while capacity remains.)
• Increase the weekly allowance. (This postpones the same cutoff without addressing continuity.)
• Provide recurring reset credits. (This offers occasional relief but retains the possibility of a complete interruption.)

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

1. A developer has consumed approximately 80% of their weekly allowance.
2. They need to begin a substantial refactor but must reserve capacity for emergency production fixes.
3. Under the current cutoff, they postpone the refactor because exhausting the allowance could leave them without access.
4. With a “Velocity” limit, they can proceed knowing that access will remain available at reduced speed.
5. If an emergency requires full speed, they can choose to purchase extended usage.
6. Otherwise, they continue within their subscription budget while capacity replenishes.

Additional Context

Additional Context

“Velocity” is the specific term I am proposing for this usage model. It describes the rate at which users can continue working as available capacity changes.

This request concerns the subscription usage policy shared by Claude Code and other Claude interfaces.

The current cutoff feels like an artificial ceiling that pushes users toward extended usage charges. Paid extended usage should remain an option for restoring full speed, alongside continued reduced-speed access for subscribers who do not want additional charges.

Related requests include the following.

• #93940 requests a larger weekly allowance for normal single-developer use.
• #94577 requests protection against active agent runs being terminated by usage limits.
• #100130 requests recurring reset credits for Max subscribers.
• #42853 requests replenishment when the subscription billing cycle renews.

These requests describe related problems but propose different solutions. The “Velocity” limit would replace the weekly cutoff with continuously replenishing capacity and progressive throttling, allowing development to continue after the full-speed allowance is exhausted.