Skip to content

[Bug] Rate limit prompt shown despite 0% usage on Max plan #28832

Closed as duplicate

Description

@yuxi-liu-wired

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report
  • I am using the latest version of Claude Code

What's Wrong?

Claude Code repeatedly shows the /rate-limit-options prompt (stop and wait / add funds / upgrade plan) despite my Max plan showing 0% usage across all metrics:

  • Current session: 0% used
  • Weekly limits (all models): 0% used
  • Sonnet only: 0% used (never used)

Restarting Claude Code does not resolve the issue. The rate limit prompt reappears immediately.

Usage Dashboard Screenshot

Plan usage limits
Current session: 0% used
Weekly limits (All models): 0% used
Sonnet only: 0% used
Extra usage: $50.01 spent (resets Mar 1)
Monthly spend limit: Unlimited

Expected Behavior

With 0% plan usage, Claude Code should accept prompts normally without showing rate limit options.

Actual Behavior

Claude Code immediately presents the rate limit options menu on every prompt:

❯ /rate-limit-options
What do you want to do?

❯ 1. Stop and wait for limit to reset
  2. Add funds to continue with extra usage
  3. Upgrade your plan

Steps to Reproduce

  1. Open Claude Code (Max plan, 0% usage)
  2. Send any prompt
  3. Rate limit options appear despite no usage

Environment

  • Plan: Max
  • Claude Code version: 2.1.59
  • OS: Ubuntu 24.04.4 LTS (x86_64)
  • Installation method: Native binary

Notes

Activity

  1. github-actions commented on Feb 26, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. CLI returns "API Error: Rate limit reached" on every command including logout (native binary, Max plan) #27336
    2. [BUG] CLI-only "API Error: Rate limit reached" on every request despite 97% quota remaining (Max 20x plan) #28096
    3. [BUG] Task tool subagents permanently return 'Rate limit reached' with 0 tokens consumed #27053

    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. added
    duplicateThis issue or pull request already exists
    and removed
    bugSomething isn't working
    has reproHas detailed reproduction steps
    platform:linuxIssue specifically occurs on Linux
    on Mar 1, 2026
  3. github-actions commented on Mar 1, 2026

    @github-actions

    This issue has been automatically closed as a duplicate of #27336.

    If this is incorrect, please re-open this issue or create a new one.

    🤖 Generated with Claude Code

  4. github-actions commented on Mar 10, 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.

  5. locked as resolved and limited conversation to collaborators on Mar 10, 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

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions