[ISSUE] Not getting Opus usage in line with the Help Center article
Resolved 💬 10 comments Opened Oct 9, 2025 by ahnaineh Closed Jan 10, 2026
Opus usage limits with the Max plan are in line with what's in the Help Center article: https://support.claude.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan. There was a bug earlier where we said in the UI that you hit your Opus limit but it was actually a weekly limit, this is now fixed. It's unrelated to rate limits and was a UI bug. We highly recommend Sonnet 4.5 -- Opus uses rate limits faster, and is not as capable for coding tasks. Our goal with Claude Code is to give everyone as much as possible of the best experience by default, and currently Sonnet 4.5 is the best experience, based on SWE Bench, user feedback, and team vibes. Please let us know if you're not getting Opus usage in line with the Help Center article.
_Originally posted by @bcherny in #8449_
@bcherny as you requested, here I'm letting you know.... Reaching weekly limit within a 2 nights coding sessions isn't in line with the Article
The Article (Max 20x):
Max 20x ($200/month): Average users can send approximately 900 messages with Claude every five hours, OR send approximately 200-800 prompts with Claude Code every five hours. Most Max 20x users can expect 240-480 hours of Sonnet 4 and 24-40 hours of Opus 4 within their weekly usage limits. This will vary based on factors such as codebase size and user settings like auto-accept mode.
Heavy Opus users with large codebases or those running multiple Claude Code instances in parallel will hit their limits sooner.
Model access: Max plan subscribers can use Sonnet or Opus 4 on Claude Code (switch between them using the /model command).
Best for: Everyday use with larger codebases, or power users.
I can assertively say we are getting no where near "24-40 hours of Opus 4 within their weekly usage limits"
This issue has 10 comments on GitHub. Read the full discussion on GitHub ↗