[Bug] Session usage quota consumed disproportionately on minimal Sonnet interactions

Resolved 💬 2 comments Opened May 20, 2026 by bharat-parihar Closed Jun 18, 2026

Bug Description
Hello, I'm reporting what appears to be a usage-accounting issue with Claude Code that is consuming my entire session limit far faster than expected. What's happening: In two separate, freshly started sessions, using Sonnet only, a single message in each session consumed close to 100% of my session usage. That is two short interactions total — not a long, context-heavy session — yet the full window was exhausted. Why I believe this is a bug, not normal usage: - Both sessions were started fresh (no accumulated context, no prior file reads or diffs carried forward). - Only Sonnet was used (not Opus). - The workload was minimal: one message per session. - This is consistent with other reports of session limits being exhausted abnormally fast since around March 23, 2026, including users seeing large single-prompt jumps in usage (e.g., GitHub issues anthropics/claude-code #38335 and #54750). Expected behavior: Two short messages in fresh Sonnet sessions should consume only a small fraction of the session window. Actual behavior: Usage jumped to ~100% and Claude Code was blocked with the usage-limit message. Account and environment details: - Account email: claudecodernr@gmail.com - Plan: Max 5x - Claude Code version: 2.1.144 - Operating system: macOS 14 - Approximate dates and times of the two sessions (with timezone): 19 May 18:00 IST Request: Could you please investigate why these two minimal sessions consumed the full quota, and restore or credit the usage that was incorrectly counted? I'm also happy to provide session IDs, transcripts, or any diagnostic output that would help. Thank you for looking into this. Best regards, Bharat Singh Parihar-RnR

Environment Info

  • Platform: linux
  • Terminal: antigravity
  • Version: 2.1.144
  • Feedback ID: 2996b6c3-8ba9-4394-bbfa-05199bf0a848

Errors

[]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗