Skip to content

[BUG] claude limit reached in less than one hour on opus 4.1, windows, v2.0.1 #8835

Closed as not planned

Description

@sorcrr2023

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

limit reached with "Claude AI usage limit reached|1760004000"

on the claude opus max $200 plan.

What Should Happen?

this shouldnt happen

Error Messages/Logs

Claude AI usage limit reached|1760004000

Steps to Reproduce

run on opus 4.1 for 45 mins

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

cant check last i was on 2.0.1

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Cursor

Additional Information

cant investigate costs or actual credit usage. i havent really been using cc that much in comparison to my use in the past. the error doesnt state anything about 5 hour limit or weekly limit. will try to open a new claude terminal and check if this is just a bug in this current session.

Activity

  1. acoutts commented on Oct 3, 2025

    @acoutts

    I think i'm seeing the same thing- "Approaching Opus usage limit" in the terminal, about 1 hour after I switched to try out opus and the usage page says i've used 20% of my opus limit that doesn't reset for another week!

  2. github-actions commented on Oct 3, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] Opus usage limit reached unusually fast with Max 20x plan since Claude Code v2 #8449
    2. [BUG] /usage shows 47% weekly used in 3 hours of Opus. Max plan.. should be 40 hours per week #8604
    3. [Bug] Anthropic API: Rapid Usage Limit Exhaustion with Claude Opus #8644

    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

  3. sorcrr2023 commented on Oct 3, 2025

    @sorcrr2023
    Author
    Image

    see image - says resets on thursday, which implies that in one day i used up the entire allocation? not sure if thats a bug or there are new reduced limits. fyi never hit a single limit yesterday. maybe used it for 5 - 8 hours. today for less than an hour.

  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. 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.

  6. 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.

  7. 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.

  8. 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

    area:apiarea:costautocloseIssue will be closed automaticallybugSomething isn't workinghas reproHas detailed reproduction stepsplatform:windowsIssue specifically occurs on Windows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions