twitter.com
August 22, 2026
1 min read
55/100
Summary
Anthropic has reportedly enrolled Fable 5 sessions running Claude Code version 2.1.236 or later in a server-side experiment that reduces the product’s effort scale. Older Claude Code versions and Opus 5 are reportedly not affected. The change is likely an A/B test, according to the X post, so it may not appear for every user. Users for whom the “high” effort setting behaves more like the previous “low” setting may be part of the test group.
What the discussion said
The thread is less interested in the displayed effort number than in whether Claude Code's higher reasoning modes have become visibly worse in real work. Several developers describe simple edits expanding into long, costly agent detours: container setup, broad repository inspection, and test construction that add nothing when the requested outcome is a single configuration-file change. Others say medium effort now beats high or extra-high effort because the latter is more likely to wander, overthink, or produce confident but wrong work. Some have responded by downgrading expensive subscriptions and using competing models to repair Claude's mistakes. An Anthropic team member says the current experiment only changes how an internal numeric effort value is mapped, not the selected effort or model quality, and points users toward feedback reports for reproducible regressions. That clarification won some appreciation, but it did not settle distrust. Commenters connect perceived quality swings to opaque routing, load management, usage limits, and token-based billing, arguing that providers can quietly alter the product while customers cannot independently audit what they received. The recurring practical conclusion is stark: AI coding agents are useful only when they stay scoped, predictable, and cheaper than supervising their unnecessary reasoning.
Where opinion split
The sharp dispute is whether the apparent degradation is merely a harmless effort-scale remapping or evidence that Claude is being quietly optimized away from reliable coding performance. Anthropic's case is that evaluations show no model-quality change and reports of clear regressions should be investigated. Skeptics counter that repeated real-world failures, time-dependent quality swings, and excessive token burn are exactly what a clean internal evaluation can miss.
Community Sentiment
Positives
Concerns