[USAGE-LIMITS] 5-Hours and Weekly Limits, Claude Negatives

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

As a loyal Claude Pro subscriber, I've been a paying customer for about a year, renewing my subscription each month. Initially, the service felt unlimited. The five-hour usage cap was more of an inconvenience, a forced pause that, while annoying, encouraged me to take breaks – a reasonable trade-off. However, in recent months, the introduction of a "weekly limit" has become incredibly frustrating. It's no longer just the hourly five-hour restriction; now, there's the constant worry of hitting the weekly limit, which can halt my work and problem-solving for an entire week.

I decided to track my Claude Code usage, which I rely on most. I measured my productive time from zero usage until I hit the weekly limit, and the result was shocking: only about 24 hours of continuous use. Considering a month has four weeks, and I hit the limit after roughly 24 hours, my $20 monthly Pro subscription effectively provides only four days (96-hours) of usable time. A full month's subscription for a mere four days of access is, frankly, outrageous and completely unacceptable.

I'm essentially locked into using Claude because its Sonnet model is the only one I can depend on for effective communication and project completion.

This situation is unacceptable. The five-hour limit was manageable. The weekly limit is an unnecessary and unwelcome addition.

Proposed Solution

I'm requesting a solution to the current usage restrictions for Pro users. Either eliminate the weekly limit entirely, or substantially increase the allowed usage to a reasonable level. It's not right to push users towards the Max plan, which costs $200 monthly, just to get adequate access. The Max plan's advantages should be about offering unique features, not simply removing usage barriers. The current system feels unfair.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

_No response_

Additional Context

_No response_