Skip to content

[BUG] 5x Max non-peak: 10% of 5h window consumed by 2 lightweight questions (6% context), 1% by a single 3-tool-call request #40881

Closed as not planned

Description

@EulerJT

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?

On a 5x Max plan ($200/month), non-peak hours (2026-03-30 05:00 GMT-4), quota consumption is wildly disproportionate to actual
work:

Most damning data point: A single trivial request (3 tool calls: 1 failed gh issue view, 1 ls, 1 file write

  • a short text response of ~100 output tokens) consumed 1% of the non-peak 5-hour window. This is not
    explainable by any reasonable token accounting model.

In the same session, two earlier questions (a settings review with ~15-20 file reads/bash commands + a web search
with 2 Sonnet sub-agents totaling ~74K tokens) consumed ~10% of the 5-hour window, while context window
utilization was only ~6% (~60K of 1M).

The off-peak 2x promotion ended March 28 — even accounting for that, the consumption is 5-10x what it should be
based on visible token volume.

What Should Happen?

  • 3 tool calls with ~500 output tokens should not consume 1% of a 5x Max 5-hour non-peak window
  • A lightweight session (~900K total tokens, 6% context) should not consume 10% of the same window
  • Quota consumption should be proportionate to actual token usage at published API rates

Error Messages/Logs

Steps to Reproduce

  1. Start Claude Code v2.1.87 on 5x Max plan during non-peak hours
  2. Send a trivial request that triggers ~3 tool calls (e.g., "write a file to my desktop and tell me where to file an issue")
  3. Observe quota meter — expect ~2% consumption for this minimal task
  4. Alternatively: send 2 questions involving ~20 tool calls + 2 Sonnet sub-agents, observe ~10% consumption at only
    6% context utilization

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.87 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

Token breakdown

Sub-agents (Sonnet, self-reported):

  • Agent 1: 43,574 tokens, 24 tool calls
  • Agent 2: 30,453 tokens, 15 tool calls

Main context (Opus, estimated):

  • ~15-20 tool calls, each a full API roundtrip with growing history
  • System prompt: ~20K tokens
  • Thinking tokens: unknown (invisible to user)

Related issues

Context

  • 1M context enabled for weeks, was not an issue before March 28
  • effortLevel: high (unchanged, was not an issue before)
  • Off-peak 2x promotion ended March 28 — explains ~2x increase at most, not the 5-10x observed

Activity

  1. added
    invalidIssue doesn't seem to be related to Claude Code
    and removed
    bugSomething isn't working
    on Mar 30, 2026
  2. github-actions commented on Mar 30, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [Bug] Token usage calculation incorrect for *non-peak* hours with 2 small sessions #40845
    2. [BUG] Abnormal rate limit consumption — 1-2 prompts exhausting 5-hour window #38345
    3. [Bug] Max plan rate limiting: 5-hour usage limit exhausted after 3-5 requests #40698

    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. EulerJT commented on Mar 30, 2026

    @EulerJT
    Author

    This is reproducible through Claude Code CLI (v2.1.87). The quota drain is measured during Claude Code tool-call
    roundtrips, not on claude.ai web. Token breakdown and reproduction steps are provided above. Please reconsider the
    label.

  4. junaidtitan commented on Apr 13, 2026

    @junaidtitan

    Context bloat compounds silently — each turn re-sends accumulated tool outputs, progress entries, and metadata. Cozempic strips this automatically so you get more turns per rate limit window. Lossless — nothing meaningful is removed.

    pip install cozempic && cozempic init

    Feedback welcome.

  5. github-actions commented on May 24, 2026

    @github-actions

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

  6. github-actions commented on Jul 17, 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.

  7. locked as resolved and limited conversation to collaborators on Jul 17, 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

    invalidIssue doesn't seem to be related to Claude CodestaleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions