Opus 5 Day 2: Saturation self-testing trades cost for quality, total cost may beat Fable
2026-07-25 群聊日报
Third-party tests show Claude Opus 5 uses saturation self-testing—frontend screenshot checks and 1000+ backend test cases—to nearly eliminate delivery issues, but total cost in complex scenarios may exceed Fable. With self-testing off, bug rates don't beat the previous model. Anthropic's strategy: long-chain debugging over one-shot correctness. The official model card advises against max effort for the first time; FrontierBench peaks at xhigh. Another test reveals ~80% of Claude Code's system prompt was cut. Group sentiment is positive, some calling it smoother than Fable. OpenAI had a full 503 outage overnight; reset cards landed the next day. WSJ reports US companies are mixing cheaper models to control costs, with Cursor as a beneficiary.
Why it matters: Third-party testing delivers the most concrete behavioral and cost data on Opus 5 so far — the self-testing tradeoff is a real signal. Slight discount for being a group-chat digest rather than the original review, but density clears the featured bar.