Detailed Analysis
A Reddit post from r/Anthropic accuses Anthropic of deliberately allowing—or refusing to fix—a bug in which a user's full project instructions and account details are silently injected into every message sent to Claude, as though the user had typed them manually. The poster claims this bloats token usage substantially and produces degraded, "rubbish" responses. Notably, the complaint ties the bug's persistence to the timing of Fable's restoration (Fable being a known Claude-based interactive storytelling/roleplay product), implying that Anthropic has a financial incentive to leave the bug unpatched because it inflates token consumption and thus billing or usage metrics tied to that product.
The core factual claim here is difficult to verify independently: there is no corroborating documentation, changelog entry, or official Anthropic acknowledgment referenced in the post itself, and the "research context" turned up no external confirmation. What is verifiable is the pattern of user behavior this represents—a bug report escalating into an accusation of intentional malfeasance, a common trajectory in software communities when a reported issue lingers without visible resolution or communication from the vendor. The specific technical complaint (system/project context being re-sent or re-injected into every turn) is plausible as an implementation detail of how Claude's API and consumer apps manage conversation state, project knowledge, and custom instructions; poorly optimized context management could indeed cause instructions to be redundantly included in each message, consuming context window and billed tokens unnecessarily. Such an issue would be a legitimate engineering bug rather than evidence of intent, but the optics of a token-hungry bug coinciding with a paid feature's relaunch fuel suspicion regardless of the actual cause.
This complaint matters less for its specific technical merits and more as a signal of the trust dynamics between Anthropic and its user base. Token-based pricing models create an inherent structural tension: any bug that increases token consumption—even unintentionally—looks self-serving to users, especially when Anthropic (like OpenAI, Google, and other frontier labs) has faced broader criticism over model quality fluctuations, "nerfing" allegations, opaque routing between model versions, and inconsistent context-window behavior across products. Community forums such as r/Anthropic and r/ClaudeAI have repeatedly become venues where users compare notes on suspected undisclosed changes to model behavior, quantization, or system prompts, often absent any official response, which breeds exactly this kind of conspiratorial framing.
More broadly, this incident reflects a recurring theme in the deployment of commercial LLM products: the gap between complex, rapidly iterating backend infrastructure (context injection, prompt caching, project-knowledge retrieval, memory features) and the transparency users demand about how their tokens and money are being spent. As Anthropic and competitors push features like persistent projects, custom instructions, and memory, the technical surface area for bugs that silently affect billing grows, and so does the reputational risk when those bugs aren't quickly diagnosed and explained publicly. Whether or not the Fable timing is coincidental, the episode underscores why AI labs increasingly need clear bug-tracking transparency, status-page communication, and prompt/token auditing tools if they want to preempt user distrust in an ecosystem where "the model got worse" or "I'm being charged more" complaints spread quickly and are hard to conclusively prove or disprove from the outside.
Read original article →