Detailed Analysis
A Reddit post titled "I'm done with you Anthropic and OpenAI" captures a growing strain of user frustration with the current generation of frontier AI models, specifically citing a disappointing release of "Sonnet 5" and what the poster calls a "Jailed Fable 5," alongside a "lobotomized Opus 4.8." The author describes attempting a legitimate cybersecurity use case—auditing API security and generating a remediation plan—only to be repeatedly blocked by refusals or overly cautious model behavior. Frustrated, the poster claims to have switched to GLM-5.2 (a model from Zhipu AI, a Chinese AI lab) via an open-source coding tool, reporting that it outperformed Opus 4.8 on the same task at a lower token cost, and describes a sense of "freedom" in being able to discuss cybersecurity topics without friction.
The specific model names referenced in the post—Sonnet 5, Opus 4.8, GLM-5.2—do not correspond to any publicly confirmed Anthropic or Zhipu AI releases as of this writing, suggesting the post may reflect informal community naming conventions, unreleased/leaked builds, speculative version numbers, or simply user confusion about model identifiers. This is a recurring pattern in AI enthusiast communities like r/Anthropic, where version numbers get used loosely ahead of official announcements, and posts can blend genuine grievances with rumor or exaggeration. Regardless of the literal accuracy of the model names, the underlying complaint is a familiar and recurring theme in AI discourse: the perceived tension between safety-oriented refusal behavior and legitimate professional use cases, particularly in security research and penetration testing contexts where discussing exploits, vulnerabilities, or attack methodologies is standard professional practice but can trigger overly broad safety filters.
This tension matters because it sits at the center of a real design challenge for companies like Anthropic and OpenAI: calibrating models to refuse genuinely harmful requests (e.g., building malware for malicious use) without over-refusing benign professional work (e.g., a security engineer auditing their own systems). Cybersecurity professionals have long complained that safety tuning can be blunt, refusing keyword-adjacent requests regardless of context or stated intent. When users hit these walls, especially paying API customers, they experience it as a productivity tax, and posts like this one reflect a broader sentiment: the belief that safety-conscious "alignment tax" makes commercial frontier models more expensive and less capable for legitimate technical work than more permissive, cheaper alternatives.
The post also gestures toward a business-model critique—that Anthropic and OpenAI are increasingly oriented toward government and enterprise contracts, and that retail/consumer API pricing and reliability suffer as a result, with claims that companies will "reduce TPS by force" (throttle throughput) to manage costs. Whether or not this speculation is accurate, it reflects a broader anxiety among developers and power users about rate limits, pricing changes, and inconsistent model behavior across updates. This dovetails with a larger 2025-2026 trend: the rapid rise of competitive open-weight and Chinese-developed models (DeepSeek, Zhipu's GLM family, Qwen, Kimi, and others) that are narrowing the capability gap with U.S. frontier labs while undercutting them significantly on price and, in some cases, offering less restrictive content policies. As switching costs between models drop—thanks to standardized APIs, open-source agent frameworks, and tools like OpenCode—user loyalty to any single lab is becoming increasingly contingent on immediate performance and cost rather than brand, intensifying competitive pressure on Anthropic and OpenAI to justify premium pricing with tangible capability and usability advantages.
Read original article →