[BUG] $115 Total cost on Max subscription while weekly quota bar sits at 73% - charged despite available plan capacity?

Resolved 💬 2 comments Opened Jul 8, 2026 by Bernie858 Closed Jul 11, 2026

What happened

On a Max (Stripe subscription) plan, a single Claude Code session shows $115.85 "Total cost" while my plan-quota bars are well under 100% — Current week (all models) at 73% used, Current session at 33% used (reset Jul 12, 1:59pm PT). This matches the "extra usage charged despite available plan capacity" pattern in #32544 and the double-charge pattern in #23315.

I want to confirm whether real dollars were charged versus this being a cost-equivalent display, because the numbers diverge from the quota bars.

Environment

  • Claude Code (VS Code), Windows 10
  • Plan: Max, billingType: stripe_subscription
  • No ANTHROPIC_API_KEY set (verified in Machine/User/Process env); no apiKeyHelper, no Bedrock/Vertex config
  • Default model was claude-fable-5[1m] (1M-context), later switched to Opus

Usage panel (verbatim)

Total cost: $115.85
Total duration (API): 2h 25m 37s | (wall): 3h 9m 8s
Usage by model:
  claude-haiku-4-5:  14.4k in,   513 out,      0 cache read,     1 cache write ($0.0270)
  claude-fable-5:    78.4k in, 157.2k out,  38.8M cache read, 809.8k cache write ($63.60)
  claude-sonnet-5:   80.1k in, 473.8k out,  90.8M cache read,   2.4M cache write ($43.67)
  claude-opus-4-8:   18.0k in,  61.4k out,   4.6M cache read,  635.5k cache write ($8.55)
Current session:            33% used (resets 10:29pm PT)
Current week (all models):  73% used (resets Jul 12, 1:59pm PT)
Current week (Fable):       95% used (resets Jul 12, 1:59pm PT)

The question

  1. Is the $115.85 Total cost a charge to my payment method, or a cost-equivalent metric drawn against the (sub-100%) weekly plan allowance?
  2. If a charge: why, given the weekly bar is at 73% with capacity remaining? This is the exact "charged despite available plan capacity" symptom in #32544.
  3. Note the enormous cache-read volume (38.8M + 90.8M ≈ 130M tokens one session) — is cache-read metered against plan quota or billed as extra usage?

Expected

Cost display and plan-quota bars should agree; usage under 100% of a weekly allowance should not incur extra-usage dollar charges on a subscription plan.

Related: #32544, #23315

View original on GitHub ↗

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