← Reddit

Token Burn Increase...?

Reddit · Reaper_1492 · May 30, 2026
A user reported their Claude code costs doubled over the past few days without material changes to configuration or usage. Token burn increased from approximately $100 per day to $200 every 2-3 hours, while the reasoning level remained set to "extra high" without user-initiated modifications. The user suspected potential pricing or configuration changes to the Claude Opus 4.7 model may have caused the spike.

Detailed Analysis

A Reddit user posting to r/Anthropic reports a dramatic and unexplained surge in Claude Code API costs, describing a jump from approximately $100 per day — a stable figure sustained over months — to $200 every two to three hours. That represents a cost increase of roughly 14 to 16 times over a very short period, which the user attributes to no deliberate changes on their part. The user identifies themselves as operating on the model designated "Opus 4.7" and notes that the reasoning level is currently set to "extra high," a setting they claim never to have configured manually, suggesting it may have been adjusted by a platform default or update.

The most technically significant detail in the report is the mention of the "extra high" reasoning level. Extended thinking and multi-step reasoning modes in large language models consume substantially more tokens than standard inference, because the model generates internal chain-of-thought tokens — sometimes called "thinking tokens" — in addition to the final output. If Claude Code quietly changed its default reasoning tier, or if a recent model update altered how aggressively the system invokes extended reasoning on typical coding tasks, users operating at scale could experience exactly the kind of nonlinear cost explosion described here. The user's confusion about whether the setting "has always been that" suggests limited transparency in how Claude Code surfaces its own configuration to end users.

This incident highlights a recurring tension in AI developer tooling: the gap between user-facing abstraction and underlying inference economics. Claude Code, like similar agentic coding tools, often operates autonomously across multi-step tasks, and each iterative loop — planning, executing, reviewing — can independently invoke high-reasoning passes. When reasoning depth defaults shift, or when model updates alter how readily extended thinking is triggered, the cumulative billing impact compounds across those loops in ways that may not be visible until a billing dashboard update arrives. The user's experience is consistent with what happens when an agentic system runs many sequential calls at a premium reasoning tier without explicit user confirmation.

More broadly, the report touches on a structural challenge facing Anthropic as it scales Claude Code as a product. Power users who commit consistent daily spend represent a critical and price-sensitive segment; unexplained cost multiplications — even if traceable to legitimate feature changes — erode trust and create friction that can drive churn toward competitors. Transparent changelog communication around default inference settings, particularly for paid tiers of agentic tools, becomes essential at this stage of product maturity. The absence of such communication is itself a signal about where operational documentation and customer-facing tooling still need development.

Finally, the reference to "Opus 4.7" situates this incident in the context of Anthropic's continued incremental model release cadence for the Opus 4 family. Each successive point release in a model line typically brings capability improvements that may simultaneously raise baseline token consumption, change reasoning behavior, or shift default parameters in ways that downstream tooling like Claude Code inherits automatically. Without a clear versioning policy that decouples model updates from default configuration changes, users operating production workflows at scale face ongoing exposure to unpredictable cost variance — a problem that will likely intensify as agentic AI use cases deepen and daily token volumes grow.

Read original article →