Skip to content

Dramatic quota consumption increase — 20% in 10 minutes vs full day's work yesterday #41662

Closed as not planned

Description

@Filament61

Description

Dramatic and unexplained increase in quota consumption with Claude Code (Opus 4.6, Max plan $100/month, 5h window). This is starting to feel like being robbed.

Comparison: two consecutive sessions, same project

Yesterday (Session 308) — Normal consumption

  • Work done: 7 review passes × 6 agents, 28 files modified, ~2420 lines added, 14 commits
  • Duration: ~8 hours of active work
  • Quota used: Did NOT hit the 5-hour quota limit
  • Context: Full feature implementation with TDD, E2E tests, multi-agent reviews

Today (Session 309) — Abnormal consumption

  • Work done: 3 review passes × 6 agents, 9 small files, ~300 lines changed, 6 commits
  • Duration: ~30 minutes of active work
  • Quota used: 20% of the 5-hour window in the first 10 minutes
  • Context: Simple bug fix + small coding rules skill — a fraction of yesterday's workload

The math doesn't add up

Yesterday: 42 agent invocations + extensive file reads + heavy code generation → stayed under quota.
Today: 18 agent invocations on smaller files → 20% quota in 10 minutes.

Less than one tenth of yesterday's workload is consuming quota at 10x the rate. Something changed, and it wasn't communicated.

What makes this worse

A significant portion of today's quota was burned on correction passes — fixing code that Claude Code itself produced incorrectly. So I'm paying twice: once for wrong output, and again to fix it. At $100/month with a 5-hour window, every wasted token is money taken from me for work I didn't ask for.

Environment

  • Claude Code CLI v2.1.88
  • Model: claude-opus-4-6 (1M context)
  • Plan: Max ($100/month, 5h usage window)
  • OS: macOS Darwin 24.6.0

What I need

  1. A clear explanation of what changed in quota calculation between March 30 and March 31, 2026
  2. Visibility on per-call token consumption (currently hidden from the user)
  3. The quota model restored to what it was — or at minimum, advance communication when pricing/metering changes

I've been a paying customer building a real project with Claude Code for 4 months. This kind of silent degradation is unacceptable.

Activity

  1. github-actions commented on Mar 31, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] Abnormal rate limit consumption — 1-2 prompts exhausting 5-hour window #38345
    2. [BUG] Claude Max plan session limits exhausted abnormally fast since March 23, 2026 (CLI usage) #38335
    3. [BUG] Abnormal / inflated rate limit / session usage #38350

    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. Filament61 commented on Mar 31, 2026

    @Filament61
    Author

    Closing as duplicate of #38345 — added my data points as a comment there.

  3. github-actions commented on Apr 8, 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.

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