← Reddit

My weekly credits reset on 3 PM. By 3:48 PM I had used 12% of my 5 hour usage but 4% of my weekly usage. I am on Max. I can't figure out how the math can make sense here? How can 12% of my 5 hour usage be 4% of my weekly usage on Max?

Reddit · yrjokallinen · August 3, 2026
A user reported a discrepancy in credit consumption metrics after their weekly credits reset, where a simple task consumed 12% of their 5-hour usage but only 4% of their weekly usage on the Max plan. The user questioned whether this represented a bug and noted never having encountered this issue before.

Detailed Analysis

A Reddit user on Anthropic's Max subscription tier flagged a discrepancy in how Claude's usage limits are being tracked, noting that a simple task consumed 12% of their rolling 5-hour usage window but registered as 4% of their weekly allotment within just 48 minutes of the weekly reset. The poster's confusion is mathematically well-founded: if 12% of a 5-hour window equates to only 4% of a full week's budget, the implied ratio suggests the weekly pool is roughly three times larger than what a single 5-hour window would allow if used continuously — a ratio that doesn't obviously align with the number of 5-hour windows in a week (which would be over 33, given 7 days × 24 hours ÷ 5). This kind of math mismatch is exactly the sort of thing that erodes user trust in usage-based pricing systems, especially for paying Max subscribers who expect predictable, transparent consumption tracking.

This complaint sits within a broader pattern of user frustration around Anthropic's tiered usage limits for Claude Pro and Max subscribers. Since introducing weekly rate limits in 2025 alongside the existing 5-hour rolling windows, Anthropic has faced recurring criticism that the two metering systems don't behave consistently or transparently. Users on forums like Reddit and Anthropic's own community boards have repeatedly reported that usage percentages shown in the Claude interface seem to shift unpredictably depending on which model is used (e.g., Claude Opus vs. Sonnet), the length of conversation context, or background system load — variables that aren't always clearly disclosed to end users. The lack of a public, itemized breakdown of how "usage" is calculated (tokens processed, compute time, model tier, etc.) leaves users reverse-engineering the math from limited UI signals, as this poster is attempting to do.

The stakes here are significant because Anthropic, like OpenAI and other frontier AI labs, is under commercial pressure to manage the enormous compute costs of running large language models while still offering subscription tiers that feel fair and predictable to paying customers. Max, Anthropic's premium tier launched to compete with power-user offerings from competitors, is specifically marketed toward heavy users such as developers and researchers who rely on Claude for sustained, complex work. When usage accounting appears inconsistent or opaque — especially in ways that make it hard to plan work sessions around remaining quota — it undermines the core value proposition of a premium tier: predictable, high-volume access. Complaints like this one, even if rooted in a UI display quirk rather than an actual billing bug, generate reputational friction that competitors can exploit.

More broadly, this incident reflects a maturing tension in the AI industry between the technical complexity of usage-based compute billing and the need for consumer-facing simplicity. As frontier labs push users toward more expensive, capability-rich models (like reasoning-heavy or agentic modes), the cost per interaction becomes harder to communicate in a single, intuitive percentage. Anthropic will likely face continued pressure to publish clearer documentation on how weekly versus rolling usage windows are calculated, particularly as it courts professional and enterprise users who need to budget compute costs precisely — a transparency gap that, left unaddressed, could become a competitive liability as rivals refine their own metering and billing UX.

Article image Read original article →