Weekly usage limits introduce severe friction to development and high-intensity workflows. Hitting a weekly quota early in a sprint locks users out for days, halting productivity. Transitioning to daily limits or rolling 24-hour windows provides predictable, daily-refreshing access better aligned with real-world iteration cycles.
Key Issues with Weekly Caps
-
Burst Workflows: Coding, debugging, and deep-context tasks occur in intensive bursts rather than equal distributions across 7 days.
-
Token Drain: Agentic tasks and large repository reads consume quota rapidly, making weekly budgeting nearly impossible.
-
Severe Lockouts: Exhausting a weekly cap on day two leads to a multi-day lockout before reset.
Proposed Changes
-
Daily Reset: Replace multi-day/weekly hard caps with a 24-hour rolling usage limit.
-
Clear Reset Timestamps: Show exact daily reset times and current token/message usage directly in account settings.
-
Rollover Capability (Optional): Allow a minor percentage of unused daily quota to carry over for heavy release days.