Preflight Checklist
What's Wrong?
What's Wrong?
Since the recent update that increased/doubled the 5-hour usage limits in Claude Code, weekly limits are getting consumed significantly faster than before.
Before this update, weekly usage felt much more stable and predictable. After the change, even though the short-term 5-hour allowance appears larger, the weekly quota now drains much faster during normal usage patterns.
The effective weekly capacity feels noticeably lower than it previously was. This creates a situation where users appear to have more short-term access, but in practice hit weekly limits much earlier than before.
Main observed issues:
- Weekly limits deplete noticeably faster after the update.
- Effective weekly usage capacity feels reduced.
- Usage pacing throughout the week feels inconsistent compared to previous behavior.
- The increased 5-hour limits may have unintentionally affected weekly quota calculations or weighting.
What Should Happen?
What Should Happen?
The increased 5-hour limits should not cause weekly limits to drain disproportionately faster.
Weekly quota behavior should remain consistent with previous usage patterns, or at minimum scale fairly with the updated short-term limits so that users are not reaching weekly limits significantly earlier under similar usage conditions.
Error Messages/Logs
## Error Messages/Logs
No direct error messages are shown. The issue is related to quota consumption behavior and weekly usage depletion rate.
Steps to Reproduce
Steps to Reproduce
- Use Claude Code normally across multiple sessions during the week.
- Compare current weekly quota depletion behavior with behavior before the recent 5-hour limit increase update.
- Observe that weekly limits decrease significantly faster despite similar usage intensity.
- Notice that the effective weekly allowance feels lower than before the update.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
before usage doubling for session limits
Claude Code Version
2.1.133
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
This does not appear to be a visual/UI issue. The actual weekly quota consumption behavior seems different after the update. It would be helpful if the team could investigate whether weekly quota calculations, token weighting, or background accounting behavior changed alongside the increased 5-hour limits.
The current behavior makes weekly limits feel significantly more restrictive despite the advertised increase in short-term availability.
Preflight Checklist
What's Wrong?
What's Wrong?
Since the recent update that increased/doubled the 5-hour usage limits in Claude Code, weekly limits are getting consumed significantly faster than before.
Before this update, weekly usage felt much more stable and predictable. After the change, even though the short-term 5-hour allowance appears larger, the weekly quota now drains much faster during normal usage patterns.
The effective weekly capacity feels noticeably lower than it previously was. This creates a situation where users appear to have more short-term access, but in practice hit weekly limits much earlier than before.
Main observed issues:
What Should Happen?
What Should Happen?
The increased 5-hour limits should not cause weekly limits to drain disproportionately faster.
Weekly quota behavior should remain consistent with previous usage patterns, or at minimum scale fairly with the updated short-term limits so that users are not reaching weekly limits significantly earlier under similar usage conditions.
Error Messages/Logs
## Error Messages/Logs No direct error messages are shown. The issue is related to quota consumption behavior and weekly usage depletion rate.Steps to Reproduce
Steps to Reproduce
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
before usage doubling for session limits
Claude Code Version
2.1.133
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
This does not appear to be a visual/UI issue. The actual weekly quota consumption behavior seems different after the update. It would be helpful if the team could investigate whether weekly quota calculations, token weighting, or background accounting behavior changed alongside the increased 5-hour limits.
The current behavior makes weekly limits feel significantly more restrictive despite the advertised increase in short-term availability.