Qwen3.8 Max Is on Writingmate: Testing Alibaba's 2.4-Trillion-Parameter Flagship on Agentic Coding and Tool Use

Alibaba has a habit of announcing "second only to the frontier" a few weeks before anyone can check the math. It did it with Qwen3.7-Max in May, it did it with the Qwen3.8-Max preview on July 19, and on August 3 it did it again — except this time the full model shipped, with a real benchmark table attached instead of a promise. Qwen3.8 Max is now generally available: 2.4 trillion parameters, a 1-million-token context window, and Alibaba's biggest model to date, live in the Writingmate catalog the same week it launched.

My name is Artem, and I run the Writingmate blog. Every time a model this size lands, I run it through the same three-task suite I've used on DeepSeek V4 Pro, Mistral Large 3, and Muse Spark 1.1: a broken function with a misleading stack trace, a messy module that needs an honest refactor, and a multi-step job that only works if tool calls actually chain together. Qwen has a real reputation problem here — its own July preview got called a "benchmark specialist" on Hacker News before a single independent number existed. So I wanted to see how much of the August 3 release actually holds up once you stop reading the announcement and start giving it work.

What Qwen3.8 Max Actually Is

Qwen3.8 Max is a sparse Mixture-of-Experts model, the general-availability successor to the Qwen3.8 Max Preview that Alibaba showed off at WAIC in Shanghai on July 19. The total parameter count is 2.4 trillion — Alibaba still hasn't published the active-parameter count, which is the number that actually determines inference cost and speed, and its silence on that specific figure is the one gap in an otherwise unusually detailed spec sheet.

Here's what is documented: a 1-million-token context window (991K tokens of input, 983K with thinking mode on), up to 131K tokens of output, and a reasoning budget that can run as high as 262K tokens. It takes text, image, and video as input and returns text. Reasoning is mandatory rather than optional — there's no way to fully turn off the "thinking" pass, and it defaults to the highest effort setting, which matters if you're used to toggling reasoning off for quick, cheap replies.

The multimodal side is where Alibaba is putting its actual weight. It scored 92.1 on OmniDocBench 1.5 and 91.5 on Parametric CAD Bench, and on Arena.ai's Vision leaderboard it ranks #2 overall — behind only Claude Fable 5 at high reasoning effort, and ahead of every Claude Opus variant, Gemini 3 Pro, GPT-5.5, and Grok 4.5. That's a real, third-party-scored result, not a self-reported claim, and it's the strongest single data point in the whole launch.

The Benchmark Claims vs. What's Actually Verified

Alibaba's own framing for the July preview was that Qwen3.8 is "one of the most powerful models available today... second only to Fable 5." That line traveled fast on X and got picked apart just as fast, because it shipped without a benchmark table, an active-parameter count, or a license. By the August 3 GA release, Alibaba backed it up with numbers — but the picture those numbers paint is more mixed than the tagline suggests.

On Terminal-Bench 2.1, Qwen3.8 Max scores 86.6, ahead of Claude Opus 4.8 and Claude Fable 5 (84.6) but behind GPT-5.6 Sol (88.8). On SWE-bench Pro, a benchmark that's specifically about fixing real GitHub issues in real repositories, it drops to 67.7 against Fable 5's 80.0 — a gap that matters a lot more for anyone actually shipping code than a terminal-navigation score does. On Arena's Frontend Code leaderboard it lands at #4 with 1,668 points, trailing Claude Opus 5 (Max) at 1,705 and Kimi K3 (Max) at 1,676, and roughly tied with Claude Opus 5 at high effort.

"Big news: Qwen3.8-Max just landed at #4 on the Frontend Code Arena leaderboard with a score of 1,668! With 1,668 points, Qwen3.8-Max is trailing only Claude Opus 5 (Max) with 1,705 pts and Kimi K3 (Max) with 1,676 pts, on par with Claude Opus 5 (High) with 1,669 pts. It also ranks #2 in Consumer Product, #3 in Brand & Marketing, Reference-based design, Gaming, and Content Creation Tools." — Arena.ai on X

So the honest read: Qwen3.8 Max is a genuine top-five-ish model on general reasoning and a genuine top-two model on vision, but it is not, on the evidence that's actually public, "second only to Fable 5" on coding specifically. That distinction — strong generalist and multimodal model, mid-pack on hard software-engineering benchmarks — is the thing the marketing headline glosses over, and it's exactly why I wanted to run it through tasks that look like real work instead of trusting the leaderboard position alone.

How I Tested It: Three Tasks, No Cherry-Picking

I used the same suite I've run on every recent flagship launch, through the Qwen3.8 Max endpoint in Writingmate's model catalog, with reasoning left at its default (mandatory, high effort):

• Broken function, misleading trace: a Python function where the actual bug is two calls upstream of where the exception fires, so a model that just patches the crash site fails.
• Messy refactor: a 300-line module with duplicated logic, inconsistent naming, and one silent bug hiding in the duplication, with instructions to clean it up without changing behavior.
• Multi-step agentic job: a task that requires reading a file, calling a search tool, using that result to call a second tool, and writing output that depends on both — a real test of whether tool calls chain coherently rather than getting reset between turns.

Qwen3.8 Max's reasoning trace on the broken-function test was long — noticeably longer than DeepSeek V4 Pro's on the same prompt — but it correctly traced the bug back through both upstream calls on its first attempt, rather than patching the crash site and declaring victory the way a couple of other recent launches did. The mandatory reasoning step is clearly doing real work here, not just padding the response.

The refactor task is where the SWE-bench Pro number started to feel real. Qwen3.8 Max cleaned up the naming and collapsed the duplicated logic, but it missed the silent bug hiding inside the duplication — the same bug DeepSeek V4 Pro caught in its own test run. That's a small, specific miss, but it's consistent with a model that's stronger at broad reasoning than at the kind of close-reading software-engineering work SWE-bench Pro is built to measure.

The multi-step tool-use test was the strongest result of the three. The model chained the file-read into the search call and correctly used the search result to inform the second tool call without losing track of the original goal — the exact failure mode that trips up models with weaker native tool-calling. Given that Alibaba is separately claiming Qwen3.8 Max held together a 16-day autonomous coding run against a public GitHub repo (265 commits, 127 pull requests, audited and public under the qwen-code-dev-bot account), a solid short multi-step chain isn't surprising, though a single afternoon of testing obviously can't confirm a 16-day claim either way.

Where the 1M-Token Context Window Actually Helps

A 1M-token window is only useful if the model can actually find and use the right piece of it, and this is a place where I did notice a real advantage. I fed it a larger multi-file codebase context than any of the three core tasks strictly required — deliberately more than needed, the way you'd end up doing in a real project where you paste in a whole module for context — and it correctly pulled a naming inconsistency between two files that wasn't part of the stated task, flagging it as a likely bug rather than ignoring it. Muse Spark 1.1 did something similar in my earlier test of its own 1M-token window; it's a genuine advantage for large codebases with context scattered across many files, not just a marketing number on a spec sheet.

Qwen3.8 Max vs. the Field

Here's how the published numbers stack up against the models I've already put through this same suite, plus the two frontier models Alibaba is explicitly comparing itself to:

Model	Total / Active Params	Context Window	Terminal-Bench 2.1	SWE-bench Pro	Input / Output Price (per 1M tokens)
Qwen3.8 Max	2.4T / undisclosed	1M tokens	86.6	67.7	$2.00 / $6.00
GPT-5.6 Sol	Undisclosed	~400K tokens	88.8	—	Higher (frontier tier)
Claude Fable 5	Undisclosed	~500K tokens	84.6	80.0	Higher (frontier tier)
DeepSeek V4 Pro	Undisclosed MoE	128K tokens	Not directly comparable	Strong on close-reading tasks in my own tests	Aggressively priced
Mistral Large 3	675B / 41B	256K tokens	Not directly comparable	Mixed independent results	Cheaper, open Apache 2.0

Alibaba's pricing is the one place where the "on par with the frontier" pitch clearly lands: $2.00 per million input tokens and $6.00 per million output tokens, with cached input at $0.25 — roughly 40% of Claude Opus 5's input price and about a quarter of its output price internationally. If your workload is mostly long-context reasoning and multimodal document work rather than tight software-engineering fixes, that price-to-capability ratio is genuinely competitive, and you can check the current numbers on the Qwen3.8 Max model page or run a side-by-side against DeepSeek V4 Pro on the Writingmate pricing page before committing a workflow to it.

Community Reaction: Excitement, Then the Usual Caveats

The pattern on r/LocalLLaMA has been consistent across both the July preview and the August GA release: real interest in another frontier-scale open effort, immediately qualified by "wait for the independent numbers." Alibaba has promised open weights for Qwen3.8-Max "next week" as of the GA date — the first time it's committed to open-sourcing a model at Max scale — and that's the detail actually driving the self-hosting conversation, more than the headline parameter count.

"2.4T is a nice number for a press release, but the thing I actually care about is whether the open weights show up and whether anyone outside Alibaba can serve it on anything short of a small data center. Watching for the SWE-bench and Terminal-Bench numbers to get reproduced before I move anything real onto it." — u/moe_router on r/LocalLLaMA

On Hacker News, the sharper version of the same skepticism showed up around the "second only to Fable 5" line specifically: that kind of ranking claim is exactly what a public benchmark table exists to settle, and Alibaba's own SWE-bench Pro number — 67.7 against Fable 5's 80.0 — is the evidence that undercuts its own tagline. Treat the coding-parity claim as marketing until more third parties score it independently, the same way you'd treat any single-lab benchmark claim on launch day.

Should You Actually Use It?

Based on what I saw, Qwen3.8 Max is a strong pick for three specific situations: multimodal document and visual reasoning work, where its Arena Vision ranking is real and independently scored; long-context tasks where you're pulling from scattered files or lengthy source material and need the model to actually use what it's given rather than lose track of it; and budget-sensitive workloads where you want frontier-adjacent reasoning without frontier-tier pricing. For tight, close-reading software-engineering fixes — the kind SWE-bench Pro is built to measure — DeepSeek V4 Pro held up better in my own side-by-side testing, and it's worth running the same prompt through both before you standardize on one.

The easiest way to find out which one fits your actual workflow is to run them side by side. Qwen3.8 Max is live now in the Writingmate model catalog, and you can switch between it, DeepSeek V4 Pro, Mistral Large 3, and Claude Opus 5 mid-conversation in the same chat window without juggling separate subscriptions or API keys for each provider — genuinely the fastest way to sanity-check a "second only to the frontier" claim yourself instead of taking a press release's word for it.

Alibaba shipped a real model with real, mostly-verified numbers this time, which is more than the July preview offered. It's just not quite the model the headline claims it is — and that gap between the tagline and the SWE-bench Pro score is worth knowing before you pick it for a coding-heavy workflow specifically.

See you in the next one!

Artem