Sonnet Usage = All Models Usage??

Detailed Analysis

A reported anomaly in Anthropic's Claude Code platform has drawn attention from subscribers of the Max 20x tier, who have observed that usage attributed to Claude Sonnet 4.6 appears to match — or nearly match — the "All Models" total usage counter, raising questions about whether the platform's usage tracking system is functioning as intended. The original post, shared on the r/ClaudeCode subreddit, also notes a close alignment between Sonnet 4.6 usage figures and those of Opus 4.7, further suggesting that something in the metering or display logic may be conflating distinct model-specific counters into a single aggregated figure.

According to research and corroborating reports on Anthropic's GitHub issue tracker, this behavior reflects a confirmed bug in the Claude Code CLI. When a user selects only the Sonnet model for their session, usage is being deducted from both the Sonnet-specific usage counter and the broader "All Models" usage counter simultaneously — a form of double-counting that makes Sonnet's reported totals appear to mirror overall usage. In reality, Anthropic's platform maintains separate tracking for individual models such as Claude Sonnet 4.6, Claude Opus 4.7, and Claude Haiku 4.5, each subject to distinct rate limits and rolling usage windows. The "All Models" counter is meant to represent aggregate consumption across the full model suite, not a replica of any single model's usage.

The significance of this bug extends beyond mere display inaccuracies. For high-volume subscribers on the Max 20x plan, accurate usage tracking is operationally critical — particularly for developers and teams running agentic workflows or large-scale coding tasks in Claude Code, where Sonnet 4.6 is positioned as the recommended model for balanced throughput. Misleading usage data can cause users to incorrectly perceive that they are hitting overall platform limits when they may only be approaching model-specific thresholds, or vice versa, potentially disrupting workflows and complicating capacity planning.

This incident sits within a broader pattern of growing pains as Anthropic scales Claude's infrastructure to support increasingly complex, multi-model deployment environments. As the Claude ecosystem expands — with distinct models optimized for different use cases and subscriber tiers carrying differentiated access rights — the backend systems responsible for quota management and usage attribution face mounting complexity. Bugs of this nature underscore the challenge of maintaining granular, accurate accounting across a diverse model portfolio, particularly as rate limiting logic must account for rolling time windows, weekly caps, and tiered subscription structures simultaneously. Anthropic's transparency through public GitHub issue tracking at least signals an active awareness of such infrastructure gaps, and users experiencing the discrepancy are advised to consult the official API documentation and platform dashboard while the underlying issue is resolved.