Skip to content

[BUG] Max x20: CLI still shows Rate limit reached after weekly reset time passed #26821

Closed as not planned

Description

@pavelbe

Preflight Checklist

  • I searched existing issues and did not find a precise report for this post reset behavior.
  • This is a single bug report.
  • I am using the latest available Claude Code version on my machine.

What Is Wrong?

This is a follow up to #26812.

The weekly reset time passed in Usage, but Claude Code CLI still returns API Error: Rate limit reached for every prompt.

Initial symptom was already reported in #26812. After waiting for the weekly reset boundary to pass, the error still persists. So this is not only a pre reset mismatch, it also continues after reset.

What Should Happen?

When the weekly reset time has passed, backend limiter state should refresh and CLI prompts should be accepted.

Error Messages and Logs

API Error: Rate limit reached

Steps to Reproduce

  1. Use Claude Max account in Claude Code CLI.
  2. Observe rate limit errors close to weekly boundary as described in [BUG] Max plan: CLI stuck on 'API Error: Rate limit reached' with weekly usage at 91% #26812.
  3. Wait until weekly reset time passes in Usage.
  4. Send any prompt in CLI.
  5. Observe the same API Error: Rate limit reached continues even after reset.

Environment

  • Claude Code CLI version: 2.1.47
  • OS: Windows 11 + WSL Ubuntu
  • Plan: Claude Max
  • Max tier: x20
  • Billing mode: subscription, not API key
  • Repro date: February 19, 2026

Additional Context

Please investigate weekly reset propagation between Usage dashboard and backend CLI limiter state.

Activity

  1. pavelbe commented on Feb 19, 2026

    @pavelbe
    Author

    Additional evidence (February 19, 2026):

    This further supports a post-reset limiter desynchronization scenario.

  2. github-actions commented on Feb 19, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] Max plan: CLI stuck on 'API Error: Rate limit reached' with weekly usage at 91% #26812
    2. Session permanently stuck on 'Rate limit reached' after transient rate limit #26699
    3. [BUG] Weekly Limit Not Resetting on time #16618

    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. pavelbe commented on Feb 19, 2026

    @pavelbe
    Author

    Update (February 19, 2026): re-authentication did not resolve the problem. I logged out and logged back in to Claude Code, but API Error: Rate limit reached still appears in a brand new empty chat.

    New feedback submitted via /feedback:

    • Feedback ID: bfe423c6-3844-47c3-bc88-1076a53c0f6e
    • Previous feedback ID: 836a1742-0f17-4018-bdfa-3924ac5e0156
    • New screenshot: https://ibb.co/3m7T7XyK

    Environment remains the same:

    • Claude Code 2.1.47
    • Opus 4.6
    • Claude Max x20
    • Windows 11 + WSL Ubuntu
  4. van-sprundel commented on Mar 19, 2026

    @van-sprundel

    Bump, still an issue

  5. ermajko commented on Mar 28, 2026

    @ermajko

    bump still an issue

  6. brunajunckes commented on Mar 31, 2026

    @brunajunckes

    Still an issue, has been more than 4 days it should reset and didnt! over here

  7. Morriz commented on Apr 2, 2026

    @Morriz

    Same. Bump

  8. newptcai commented on Apr 17, 2026

    @newptcai

    Hit the same problem. 5 minutes past the reset time, but still cannot use it.

    Glad that I got a Codex as backup!

  9. rndninja commented on May 4, 2026

    @rndninja

    Hit a similar problem, I am on a Team Plan at my current org. I have a premium seat. When my "Extra Usage" of $100 is also consumed, the session usage is stuck at 100% for the last 4 days! Super frustrating! Please fix this.

  10. github-actions commented on Jun 1, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  11. github-actions commented on Aug 4, 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.

  12. locked as resolved and limited conversation to collaborators on Aug 4, 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

    staleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions