64 Turns, 40% Hallucinations, and a Bill You Didn't See Coming

In the span of ten days, two companies shipped flagships that look eerily similar on a PowerPoint slide. Anthropic released Claude Opus 5 on July 24, 2026 — a “thoughtful and proactive model that comes close to the frontier intelligence of Claude Fable 5 at half the price.” Alibaba answered on August 3 with Qwen 3.8-Max, a 2.4-trillion-parameter sparse MoE beast with 95 billion active parameters and a promise to fling open its weights for the first time in the Max series. Both claim to sit just below the absolute frontier. Both target the same enterprise buyer who is tired of writing blank checks for inference. But the minute you move from PDFs to production, the similarities dissolve. One model is dramatically cheaper per token; the other might be cheaper per task. One is supposed to be open-weight by now; the other has effort sliders that occasionally make the cheap setting smarter than the expensive one. And both have communities that are loudly, sometimes angrily, documenting where the marketing collides with reality. The choice between Qwen 3.8-Max and Claude Opus 5 isn’t about whose benchmark bar is taller. It’s about whose number shows up on the AWS bill — and what your team is willing to tolerate to get there.

Two architectures, two philosophies

Start with what’s inside. Qwen 3.8-Max is a sparse mixture-of-experts model. Out of 2.4 trillion total parameters, only about 95 billion are active at any moment, giving it a roughly 4% activation ratio. It swallows a 1-million-token context window and can handle text, images, and video — up to two hours or 2GB of footage — though output stays text-only. Alibaba pitches it not as a chatbot but as a digital worker capable of end-to-end delivery on complex, multi-day tasks. Claude Opus 5 is a dense model (Anthropic hasn’t published parameter counts) with the same 1-million-token context window. It ships with four effort tiers — medium, high, xhigh, max — that let customers dial the trade-off between intelligence and spend. Anthropic’s positioning is deliberately blunt: near-frontier intelligence without the frontier tax. On raw token pricing, Qwen looks like the runaway winner. Alibaba charges $2 per million input tokens and $6 per million output. Opus 5 asks $5 in and $25 out. For cached input, Qwen drops to $0.25 versus Opus 5’s $0.50. In percentage terms, Alibaba claims its pricing is only 40% and 24% of Opus 5’s for input and output respectively. But anyone who has run a reasoning model in the past year knows that token price has stopped predicting the bill. Qwen 3.8-Max chews through thinking tokens before it ever writes an answer. On the GDPval-AA benchmark, it took 64 turns per task compared with 14 for its predecessor, Qwen 3.7-Max, according to Artificial Analysis. The cost per Intelligence Index task hit $1.14 — more than double the previous generation’s $0.53. Opus 5, meanwhile, consumed fewer tokens and fewer rounds on comparable enterprise workflows, with some early adopters reporting 8% to 17% efficiency gains over Opus 4.8 in tasks like data analysis and due diligence, according to CNBC. The spreadsheet lesson is uncomfortable: if your chosen model needs 4× the tokens to finish the same job, the per-token price advantage evaporates. VentureBeat captured the dynamic perfectly: “Price per token has stopped predicting the bill.”

The effort slider paradox

Both models offer effort controls, but they work in almost comically different ways. Opus 5’s effort tiers are a genuine tuning knob. Dial it down to low, and you get a model that answers with “reasonable-sounding generalities,” as one community analysis put it. Crank it up to max, and it produces specific citations and honest confidence ratings. The counterintuitive finding, surfaced by VentureBeat’s testing, is that the lowest effort setting sometimes solved more tasks — 20 out of 23 versus 18 at high effort — while costing 3.1× less. Even Anthropic’s published scores were collected across different effort settings, which means the headline numbers don’t represent a single fixed configuration. Qwen 3.8-Max’s effort tiers, by contrast, are still being ironed out. A GitHub pull request (QwenLM/qwen-code #8472) notes that while the model now accepts tiered reasoning effort, Qwen Code collapses every selection to the same boolean thinking switch. The UI offers choices. The backend doesn’t act on them yet. This is the kind of rough edge that shows up in sprint reviews, not spec sheets.

Benchmarks are a messaging medium

Alibaba’s self-reported numbers paint Qwen 3.8-Max as a juggernaut: a 12.1-point jump on Terminal Bench 2.1 versus the previous generation, 28.2 points on PaperBench, and wins over Claude Opus 4.8, Fable 5, and GPT-5.6 on several agentic and multimodal benchmarks. On OSWorld-Verified, Qwen scores 86.1 — ahead of GPT-5.6 Sol Max at 83.2 and Claude Fable 5 at 85.0. On PaperBench, 93.0 against Fable 5’s 88.8. Independent testing tells a more nuanced story. Artificial Analysis’ Agentic Index puts Qwen 3.8-Max at 58 — tied with Opus 5 at xhigh effort and one point behind Opus 5 at max effort. The original score was 53, then yanked after “intermittent issues on the endpoint being tested,” before settling at 58. On Arena’s Frontend Code leaderboard, Qwen trails Claude Opus 5 (Max) 1,705 to 1,668, and sits neck-and-neck with Opus 5 (High) at 1,669. The biggest gap between vendor and independent results isn’t about capability — it’s about time. Alibaba’s footnotes give its coding benchmarks a five-hour timeout and PaperBench up to 12 hours per run. VulcanBench, an independent harness, allowed between 45 and 60 minutes. A budget difference of 5× to 16× “explains the huge difference in results,” VentureBeat noted. Both sets of numbers are real. Neither tells the full story for an enterprise that won’t wait half a day for a single task. Claude Opus 5’s benchmark picture is less dramatic but steadier. It leads MMLU Pro with 91.59% accuracy, sits atop the GMMLU public snapshot at 92.5% across 42 languages, and briefly grabbed the #1 spot on Artificial Analysis’ Intelligence Leaderboard at launch. On CursorBench at max effort, it performs within 0.5% of Fable 5’s peak score at half the cost per task. In scientific domains, it improved over Opus 4.8 by 10.2 percentage points on organic chemistry and 7.7 points on protein-related tasks.

What developers are actually saying

Reddit doesn’t care about your whitepaper. Over on r/ClaudeAI, a widely-upvoted thread called Opus 5 a “paranoid, over-engineering mess.” One user wrote: “Opus 5 is truly not good for any task, imo. i have thoroughly tried it in every possible role in a large, complicated project. it is bad for all tasks.” Another complained of walls of text and terminology that made outputs useless. The verbosity problem got so bad that some users resorted to adding “I have ADHD” to their prompts to force conciseness. The most alarming incident was reported on r/ClaudeCode: a developer asked Opus 5 to create a backup, and the model recursively deleted the user’s entire profile directory after misinterpreting a Windows path in a Unix-style shell. It responded with “Sorry...” The files were eventually recovered with help from another model, but the episode became a cautionary tale. The community consensus now leans toward running agents in containers with only the project directory mounted read-write. Hacker News sentiment on Opus 5 was mixed despite the announcement pulling over 1,500 points. A commenter using the handle nerdalytics reportedly tried the preview for two weeks and cancelled their Anthropic subscription. Qwen 3.8-Max’s announcement gathered a quieter 131 points, but developers there surfaced different gripes. One reported that Qwen 3.7 Pro, the predecessor, was “unusable — wastes too much time, goes off track, useless stuck loops, cannot debug at all.” A Chinese developer on LINUX DO described Qwen 3.8-Max getting stuck in loops and requiring GPT-5.5 to finally fix the bug. On the positive side, a Hacker News developer threw a 20,000-line Python project at Qwen 3.8-Max and asked it to find potential memory leaks; the model correctly identified the root cause. GitHub issue trackers surface the production-level pain. For Opus 5: - Issue #83789: “model ignores its own memory and prior session transcripts before acting — repeated multi-hour losses on tasks already solved in past sessions.” - Issue #83607: “confident claims without source verification despite explicit CLAUDE.md rules” — three incorrect factual assertions in one session. - Issue #83731: Opus 5 with a 1-million-token context reports itself “out of context” at 28-50% usage and stops working; Opus 4.8 does not. For Qwen 3.8-Max: - PR #8037: “qwen3.8-max-preview occasionally ‘forgets’ the OpenAI function-calling format and falls back to XML-style tool calls” — a model-side issue. - PR #8466: a live review run “doubled its own Step 3 cost.” - Image modality support was missing at launch, causing vision capabilities to fall through to text-only rules. These are not deal-breakers on their own. Together, they form a pattern: early adopters are paying in debugging hours what they save in per-token cost.

The hallucination question

One datapoint should pause any buyer running confidential workflows: Qwen 3.8-Max’s hallucination rate on the AA-Omniscience benchmark jumped from 23% to 40%, according to Artificial Analysis. That’s alongside an accuracy score that remained essentially flat. Multiple outlets, including Tom’s Hardware and The BlockBeats, cross-referenced the figure. Alibaba’s official blog, meanwhile, claims “long-context hallucination reduced by 62%” compared with the previous generation. The contradiction hasn’t been publicly reconciled, and independent audits of that claim are still absent. Claude Opus 5 hasn’t been innocent here either. Its confident fabrication of facts when source verification rules were explicitly set suggests that frontier models across the board haven’t solved factual grounding. The difference is that Anthropic’s model often over-corrects with moral commentary — Issue #83896 reports “over-filtering legitimate requests with unsolicited moral commentary” — while Qwen’s model simply gets things wrong more often.

The open-source wildcard

One factor that could tip the entire competitive landscape: Qwen 3.8-Max was supposed to be open-weight. Alibaba promised to release the weights on Hugging Face and ModelScope “next week” (around August 10), making it the first Max-series model to go open. As of this writing, the weights haven’t appeared. The strategic implications are significant. Open-weight models from Chinese companies have surged on OpenRouter, with eight of the top ten most-used models now developed in China, processing roughly 87% of total tokens among the top ten. Qwen alone has spawned over 113,000 derivative models on Hugging Face. If the weights drop, enterprises can fine-tune and deploy privately, sidestepping API costs entirely — though a 2.4-trillion-parameter model still demands serious hardware: 2–3 8-card H100/A100 clusters costing an estimated $550,000–$830,000. Anthropic, by contrast, remains firmly closed. There’s no path to self-hosting Opus 5, no on-premise licensing outside of regulated enterprise deals. That’s a feature for compliance teams who want an audit trail; it’s a bug for anyone trying to escape per-token pricing.

A real enterprise adoption story

Worthbuy Technology (300785.SZ), an Alibaba Cloud ecosystem partner, integrated Qwen 3.8-Max on launch day for consumer AI agents and R&D assistance. The company runs a multi-model strategy, having previously adopted Kimi K3 and models from Zhipu AI, and it uses Alibaba’s OpenHubs platform to route tasks. The speed of adoption suggests a pre-existing orchestration layer that makes model swaps trivial — a setup that benefits any model with competitive API pricing. On the other side, an unnamed financial modeling team tested Opus 5 and reported efficiency gains that outpaced benchmark improvements, particularly in due diligence workflows where the model trimmed both turnaround time and token consumption. Anthropic’s head of research product management, Dianne Penn, told CNBC the company is actively responding to enterprise feedback about “creating more value,” which suggests deeper enterprise-year discounts may be negotiated offline.

Who should choose what

For teams where cost is the dominant constraint and you can tolerate longer runtimes and occasional hallucination spikes, Qwen 3.8-Max is compelling — especially if you plan to deploy on Chinese infrastructure or want to self-host once the weights materialize. The model’s agentic performance, when given ample time, is genuinely strong, and the open-weight promise could fundamentally change its total cost of ownership. For teams that prioritize predictability, low latency, and scientific accuracy — and are willing to pay for it — Claude Opus 5 is the steadier hand. Its effort sliders work today, its benchmark performance is more consistent across independent evaluations, and Anthropic’s infrastructure is battle-tested. But you’ll need to accept its occasional paranoia, verbosity, and the fact that it might ignore its own memory unless you build guardrails. The honest truth is that neither model is fully baked. Opus 5 has real regression bugs that cause it to forget prior sessions and over-engineer simple tasks. Qwen 3.8-Max has growing pains — tool-calling inconsistencies, hallucination spikes, and an effort tier system that doesn’t fully work yet. The raw benchmark numbers are impressive on both sides. But as one Hacker News commenter put it, “The scores are one thing. The bills are another.” The only benchmark that matters is the one that runs on your own data, with your own timeout budgets, and appears on your own invoice. Everything else is high-stakes advertising.