Detailed Analysis
A Reddit post surfacing on r/ClaudeAI documents what appears to be a reproducible server-side bug affecting multiple claude.ai accounts since approximately July 10, in which nearly every message fails instantly with an error claiming the request exceeds Claude's context limit by 4-6 million tokens. The reporting user, working with Claude itself via the Cowork feature to debug the issue, traced the problem to prompt assembly on Anthropic's servers: even a freshly created, empty conversation with no tools, connectors, memory, or attachments triggers injection of a roughly 19 MB object—equivalent to about 4.8 million tokens—into the context window before the model ever processes the actual user message. The bug reportedly spans all models and all client surfaces (web, desktop, iOS, incognito mode), while Claude Code and Cowork on the same affected account continue functioning normally, suggesting the fault lies specifically in the claude.ai consumer-facing request pipeline rather than in the underlying model infrastructure or API itself.
What elevates this from an annoying outage to a more serious incident is the billing dimension. According to the report, when the injected blob's size happens to drift below the context ceiling, the request doesn't fail—it silently succeeds, and usage-billed accounts get charged for processing millions of phantom tokens. One corroborating user reportedly described being billed around $4 for a single-word message, which is consistent with paying for several million tokens of invisible injected content rather than the actual short input. If accurate, this means some customers have potentially been billed for server-side errors entirely outside their control, without any indication in the product that anything unusual occurred, only discoverable by manually auditing the usage dashboard.
The post also highlights a structural support gap: despite six-plus days of unresponsiveness after an initial escalation from Anthropic's automated support agent ("Fin"), and despite the bug being reproducible and documented with specific request IDs, the corresponding GitHub issue was auto-labeled "invalid" because claude.ai lacks a formal public bug tracker separate from Claude Code's repository. This illustrates a recurring tension in fast-scaling AI products: engineering-first tools like Claude Code have relatively direct, technically fluent feedback channels (GitHub issues, active developer communities), while the mass-market consumer product claude.ai relies on conventional support ticketing that struggles to triage esoteric, infrastructure-level bugs reported by technically sophisticated users. The mismatch between the severity of a billing-affecting server bug and the informal, community-driven troubleshooting required to get it noticed underscores how support infrastructure often lags behind product complexity at companies scaling rapidly.
More broadly, the incident touches on trust and transparency issues that are becoming increasingly salient as AI companies move toward usage-based, token-metered billing models. As context windows grow larger (Claude's models now support very large context sizes) and backend systems become more complex—layering in memory, skills, connectors, and other injected context—the surface area for silent, costly failures expands correspondingly. Users have limited visibility into what is actually being sent to the model on their behalf, making this kind of "invisible token injection" bug particularly insidious: it can generate real charges without any observable defect in the chat interface itself. Incidents like this are likely to fuel broader calls for AI providers to offer clearer usage auditing tools, transparent context-assembly logs, and faster escalation paths for infrastructure bugs that carry direct financial consequences for customers, especially as competition intensifies among Anthropic, OpenAI, and Google over enterprise and developer trust.
Read original article →