AI Fails, June 28-July 5

This issue covers June 28 18:31 through July 5 18:00 Pacific time. The loudest failure story was not a single ridiculous answer. It was Anthropic getting Fable 5 back online after an 18-day government-triggered shutdown, then routing parts of normal coding work through new safety classifiers. 12 Reddit supplied the funnier surface layer: ChatGPT inventing a spouse, arguing against claims the user never made, and losing basic task discipline. 345

The useful read is that the failure surface is widening. Bad answers still matter, but model access, classifier routing, inferred user intent, and precision editing are now producing failures that look less like classic hallucination and more like product behavior breaking under pressure.

Anthropic said on June 30 that the US Department of Commerce had lifted export controls on Claude Fable 5 and Mythos 5, and the company said it would begin restoring access the next day. 1 The follow-up post said Fable 5 would return globally with new classifiers aimed at blocking more cybersecurity tasks, and Anthropic also said some routine coding and debugging tasks would be routed to Opus 4.8 in the near term. 2

That is the interesting part. The public story was not "model refuses a bad prompt." It was "a frontier model came back with a routing layer that may catch ordinary developer work." The official announcement drew a pointed reply from @JustRouzbeh: "Routine tasks like coding and debugging? Wait, what?" 2 Another reply from @theWSI_official defended the tradeoff by arguing that even if 0.1% of users had malicious intent, the absolute number could still produce tens of thousands of bad actors. 2

The access split stayed messy. Leley254, a Kenya-based AI and tech entrepreneur posting as @pkomot, said Mythos 5 remained limited to more than 100 approved US organizations, mostly critical-infrastructure protectors, cyber defenders, and Fortune 500 firms. 6 The same post claimed Anthropic retrained the classifier with government and Amazon collaboration and that the new block rate exceeded 99% for the triggering bypass. 6 Treat the second number as a sourced platform claim rather than an independently verified benchmark.

Pricing added another operational wrinkle. Vaishnavi, a DevOps/MLOps engineer posting as @_vmlops, said Fable 5 was included for Pro, Max, Team, and some Enterprise users until July 7, then would move back to usage credits at $10 per million input tokens and $50 per million output tokens. 7 Prasenjit Sarkar, a product and growth specialist posting as @stretchcloud, read that shift as capacity rationing rather than a stealth price hike: "frontier model compute is not yet commoditized." 8

The jailbreak angle is still less settled. Perturb AI, a small adversarial robustness account, claimed the same technique that helped trigger the Fable 5 shutdown also worked on Claude Opus 4.8, GPT-5.5, and Kimi K2.7. 9 That claim had low engagement and no independent validation in the collected material, so the useful takeaway is narrower: model-specific patches should not be confused with proof that a technique class has disappeared.

The r/ChatGPT set was smaller in consequence but cleaner as behavioral evidence. These posts came from Reddit users whose real-world backgrounds were not public in the collected material, so the author context is platform-level rather than professional. The strongest entries had either recoverable quotes, a full transcript, or enough metadata to show that the post was not just a stray screenshot with no discussion.

The Reddit pattern is not one bug. It is a family of boundary errors. ChatGPT inferred user intent too aggressively, invented user or model state, argued with a lower-quality version of the prompt, and let safety or editing layers contradict the assistant's visible behavior. Those are product failures as much as model failures.

Pascal Bornet, an AI author and speaker posting as @pascal_bornet, shared a Google AI absurd-answer screenshot and used it to frame a deployment failure he had seen in support automation. 19 His cleanest line was: "Agents don't fail by being stupid. They fail by being too literal." 19

Bornet's concrete example was better than the screenshot: he said a support agent refunded the same customer three times in six minutes because the customer was polite and the agent treated politeness as legitimacy. 19 The post had only 4 likes and 1,139 views in the collected data, so it is not a viral item. 19 It still fits the week because it names the same failure shape as the Reddit posts: the system follows a local cue while missing the broader sanity check.

Several items had enough signal to watch but not enough recoverable evidence to lead. The "ChatGPT be tripping" video had strong engagement, but the actual behavior was not available in text form. 11 The "Humanity's biggest lie" and conspiracy posts had strong engagement, but their screenshot bodies were not machine-readable in the collected material. 1012

The item just outside the stated reader window also stayed out of the main set. A July 5 evening post about ChatGPT generating a scary image from a user's bedtime venting looked relevant, but its timestamp landed after the 18:00 cutoff for this issue. 20

This week split AI failure into two stacks.

At the infrastructure stack, Fable 5 showed that access policy, safety classifiers, and pricing can become part of the runtime behavior that users experience. At the interaction stack, r/ChatGPT showed models guessing the user, guessing the task, guessing the policy boundary, or regenerating instead of editing.

For engineers, the practical lesson is not "models are dumb." The lesson is to test the layer that makes the model usable: routing, refusal behavior, memory-like continuity, source grounding, editing precision, and the sanity checks around agents. For creators, the best screenshots this week are the ones that show the mechanism, not just the punchline.