Detailed Analysis
A Reddit post in r/ClaudeAI surfaces a data point that has become increasingly common among developers using Claude for coding: token consumption is climbing sharply with each new model release, even as the number of requests stays relatively flat or declines. The user's table shows Opus 4.7 and Opus 4.8 consuming roughly 10 billion tokens each across 34,000-39,000 requests, while the apparent successor Opus 5 uses only 2.8 billion tokens across a much smaller 8,168 requests—yet the average tokens per request nearly doubles, jumping from around 257,000-284,000 to over 342,000. Two competing models, referred to as GPT-5.5 and Fable-5, show markedly lower per-request token averages (108,000 and 209,000 respectively), suggesting the user is comparing Anthropic's models against other coding-agent offerings and finding Claude's models notably more token-hungry per task.
This pattern reflects a broader shift in how frontier coding agents operate. As models like Opus grow more capable, they are increasingly used for longer, more autonomous coding sessions rather than quick, isolated completions. Agentic coding workflows—where a model reads extensive codebases, plans multi-step changes, runs tools, checks outputs, and iterates—naturally consume far more context and output tokens than traditional single-shot code generation. The rising average tokens per request likely reflects Anthropic's models being tuned for deeper reasoning chains, more extensive tool use, and longer working memory within a single agentic loop, rather than users simply submitting bigger prompts.
The economic and practical implications of this trend are significant for developers and for Anthropic's business model. Token-based pricing means that as models become more capable and are asked to do more autonomous work per request, the cost of running these agents scales accordingly, even if the number of discrete interactions goes down. This creates a tension familiar to enterprise AI buyers: newer, smarter models may reduce the need for human intervention and back-and-forth prompting, but the per-task cost can still rise if the model is doing substantially more computation and holding more context to accomplish the same goal. Anthropic has leaned into this dynamic by pricing and packaging products like Claude Code and API access around usage tiers, betting that increased capability and autonomy justify higher token spend for professional users who value fewer manual corrections over raw cost efficiency.
More broadly, this discussion fits into an industry-wide conversation about the true cost of "agentic AI." As coding assistants evolve from autocomplete-style helpers into semi-autonomous agents capable of executing multi-step engineering tasks, token consumption is emerging as a key metric—arguably more revealing than benchmark scores—for understanding real-world model behavior and cost. Comparisons like the one in this post, pitting Anthropic's Opus line against unnamed or codenamed competitors, underscore that developers are now scrutinizing not just accuracy and capability but efficiency: how many tokens a model burns to accomplish a given unit of work. As competition intensifies among Anthropic, OpenAI, and other labs building coding-focused agents, token efficiency may become as important a competitive differentiator as raw intelligence, particularly for cost-sensitive teams running these agents at scale in production environments.
Read original article →