Detailed Analysis
A Reddit post in r/Anthropic titled "Bugs and glitches on purpose" articulates a grievance that surfaces periodically across AI product communities: a user attributes a frustrating, glitch-ridden experience with Claude to deliberate design rather than ordinary software imperfection. The specific complaint centers on using Claude to generate PowerPoint slides, where the user encountered inconsistent formatting, mismatched timeline buckets across slides, and an inability for the model to view or self-correct the outputs it had generated. The user reports having to manually screenshot each iteration and feed it back into the chat, multiplying the number of exchanges needed to complete what should have been a straightforward task. Compounding the frustration, the user notes that Claude previously demonstrated the ability to render native .pptx files with proper tables and formatting, yet in this session it reverted to cruder workarounds like text boxes and stitched-together shapes masquerading as tables—inconsistency that reads to the user as a regression rather than a stable capability.
The post's central accusation—that Anthropic intentionally introduces bugs to inflate usage and revenue—reflects a broader undercurrent of distrust that has grown alongside the commercialization of AI coding and productivity tools. The user points to Anthropic's support policy of not issuing usage credits for technical glitches as circumstantial evidence of a perverse incentive structure: a model that produces flawed output requiring multiple costly follow-up prompts arguably generates more billable usage than one that succeeds on the first try. This is a serious claim without direct evidence, and it's important to note that inconsistent output, hallucinated capabilities, and degraded performance on agentic or multi-step tasks are well-documented characteristics of large language models generally, not unique to Claude or necessarily intentional. Non-deterministic generation, context window limitations, and the genuine difficulty of tasks like maintaining consistent formatting across a multi-slide artifact without visual feedback loops are more parsimonious explanations than deliberate sabotage.
That said, the underlying frustration points to a real and unresolved capability gap: Claude cannot natively "see" the visual rendering of files like PowerPoint decks it generates, meaning it operates somewhat blind to formatting errors that would be immediately obvious to a human looking at the slide. This creates a feedback loop problem where the model can't verify its own work against the actual rendered output, forcing users into a manual screenshot-and-correct cycle. This is a known limitation of current-generation AI assistants working with binary or complex file formats, and it's distinct from any conspiracy about monetization—it's a genuine technical constraint tied to how these models process and generate structured documents versus plain text.
The episode also touches on a passing reference to "Fable 5," seemingly a comparison point or alternative tool the user feels locked out of under a Claude subscription, hinting at broader frustration about feature access and perceived value-for-money in paid AI tiers. More broadly, this kind of post reflects a maturing and increasingly skeptical user base for AI assistants: as these tools get embedded into daily productivity workflows like office document creation, users are holding them to professional software standards of reliability and consistency, and are quicker to interpret failures through a lens of corporate incentive misalignment—usage-based pricing creating a moral hazard around quality. Whether or not the specific accusation of intentional bug injection is credible, the sentiment underscores real pressure on Anthropic and its competitors to be transparent about model limitations, improve tool-use feedback loops (such as enabling models to verify visual outputs), and reconsider how credit/billing policies interact with user trust when outputs are demonstrably flawed.
Read original article →