Skip to content

[ISSUE] Not getting Opus usage in line with the Help Center article #9196

Closed as not planned

Description

@ahnaineh

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"

Activity

  1. github-actions commented on Oct 9, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] /usage shows 47% weekly used in 3 hours of Opus. Max plan.. should be 40 hours per week #8604
    2. [BUG] Opus weekly limit reached within 5 hours. #9040
    3. [BUG] claude limit reached in less than one hour on opus 4.1, windows, v2.0.1 #8835

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. alex-feel commented on Oct 9, 2025

    @alex-feel

    The same here:

    1. Before Sonnet 4.5, I used Opus 4.1 ~4–6 hours a day, 5 days a week (≈20–30 hours), and never hit a weekly cap. Across ~3 months, I hit a 5-hour session limit only a few times.

    2. After Sonnet 4.5, I hit the weekly cap in 2–3 days, like many others.

    3. Today, after a reset, I ran a multi-agent test (orchestrator on Sonnet; two workers on Opus): 6m44s + 5m14s + 10m12s ≈ 22.2 minutes of Opus. Plan usage showed 11% of the weekly Opus limit. That implies ~22.2 / 0.11 ≈ 3.4 hours total for the week, roughly 6–12x below the stated 24–40 hours.

  3. ivanaguilario commented on Oct 9, 2025

    @ivanaguilario

    Same here. After 3 hours of Opus usage, hit 86% of my weekly limit.

    This is absolutely unacceptable for a $200 / month subscription. Changing the usage terms without previous notice is also anti-consumer and I'm sure in breach of some EU consumer protection acts, especially when the terms and conditions still don't reflect the new usage metrics.

    Please rectify.

  4. AU-Mark commented on Oct 9, 2025

    @AU-Mark

    I too have hit these usage limits within 5 hours, working on a super small code base project... a github action... nothing fancy, theres a total of 7 files and one python script that is less than 2000 lines.

    3 weeks ago I was able to use Opus 4.0 on a giant code base project I was working on and never ran into usage limits. Using it both at work and at home I could use it all day non-stop without hitting weekly usage limits. Its not very useful for me any longer. Had I known before I renewed my subscription I would have gone with GPT-5 instead.

    Anthropic, I dont know what you did to the usage models but this is ridiculous. You can barely work on a small code base for 5 hours doing debugging and new features before hitting the weekly limit... the value is no longer there and Sonnet 4.5 is useless for the large code base on my personal project... once my sub I just renewed is over Ill be cancelling unless this is fixed in the next month.

  5. ahnaineh commented on Oct 10, 2025

    @ahnaineh
    Author

    Today, opus weekly usage limit was reset,
    i used plan mode, even before a single line of code generation: 2% where over!!
    MAX20

  6. ivanaguilario commented on Oct 11, 2025

    @ivanaguilario

    @ahnaineh Same here. Just planned a simple feature with Opus and hit 2% usage after a few minutes of processing.

    This is not inline with the 24-40h of usage stated in the support articles.

  7. ahnaineh commented on Oct 11, 2025

    @ahnaineh
    Author

    12 hours later (i slept it was night)
    Now sitting around 31%

  8. github-actions commented on Dec 7, 2025

    @github-actions

    This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

  9. github-actions commented on Jan 10, 2026

    @github-actions

    This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

  10. github-actions commented on Jan 18, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  11. locked as resolved and limited conversation to collaborators on Jan 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions