New Weekly Usage Limits for Claude Code Subscription Users
Next month, we'll be introducing new weekly usage limits for Claude subscribers that, based on current usage patterns, will affect less than 5% of users.
Claude Code, as part of our subscription plans, has experienced unprecedented growth. At the same time, we've identified some policy-violating behaviors such as account sharing and reselling access, as well as some advanced usage patterns like running Claude 24/7 in the background, which are affecting system capacity for all users. Our new usage limits will address these issues and provide a fairer experience for all users.
What's changing: Starting August 28, we'll introduce weekly usage limits on top of existing 5-hour limits:
- Current: Usage limits that reset every 5 hours (no change)
- New: Overall weekly limits that reset every 7 days
- New: Claude Opus 4 weekly limits that reset every 7 days
- As we learn more about how developers use Claude Code, we may adjust usage limits to better serve our community.
What this means for you:
- Most users won't notice any difference. Weekly limits are designed to support typical daily usage in your projects.
- Most Max 20x users can use 240-480 hours of Sonnet 4 and 24-40 hours of Opus 4 within weekly limits. Heavy Opus users with large codebases or those running multiple Claude Code instances simultaneously will hit limits sooner.
- If you do reach weekly usage limits, you can choose to purchase additional usage at standard API rates to continue working without interruption. This is completely optional.
- You can manage or cancel your subscription at any time in settings.
We take these decisions seriously. We're committed to supporting long-running use cases through other options in the future, but until then, weekly limits will help us maintain reliable service for everyone. Max 20x subscribers can purchase additional usage at standard API rates if needed.
We also recognize that during this same period, users have encountered some reliability and performance issues. We've been working hard to fix these as quickly as possible and will continue to address any remaining issues in the coming days and weeks.