Qwen3.8-Max Open Weights Countdown: Announced, Not Shipped

Alibaba logoAlibabaImportantAugust 10, 2026Models
What happened
Alibaba confirmed on Aug 3 that Qwen3.8-Max open weights would ship 'next week' — as of Monday Aug 10, no repository exists and no license has been disclosed.
Why it matters
This would be the first open-weight Qwen Max-class model, and its 27B dense companion is the artifact most developers can actually run.
What to do
Watch the Qwen HuggingFace organization page this week; do not plan production deployments around an undelivered artifact.

The verdict: announced, not shipped. Do not plan production deployments around an undelivered, unlicensed artifact.

Alibaba's @Alibaba_Qwen(opens in new tab) account confirmed on August 3 that open weights for Qwen3.8-Max — a 2.4-trillion-parameter Mixture-of-Experts flagship with ~95B active parameters per token — would drop "next week," alongside a new 27B dense companion. That week is now. As of Monday, August 10, the Qwen organization page at Hugging Face(opens in new tab) contains no matching repository, the license text is undisclosed, and the only specific date — August 12 — comes from X user @hqmank(opens in new tab), not from Alibaba.

If it lands, this would be the first Qwen Max-tier model released with open weights — and the second-largest open-weight MoE ever, after Moonshot's Kimi K3 (2.8T parameters). That is a structural shift in the open-weight frontier. But "if" is the operative word. Alibaba has never open-weighted a Max-class model before. Every prior flagship — Qwen3-Max, Qwen3.6-Max, Qwen3.7-Max — stayed hosted-only. The base rate for delivery is less certain than the announcement implies.

Alibaba confirmed Aug 3 — weights still undelivered Aug 10

On August 3, Alibaba launched Qwen3.8-Max as a generally available API with published pricing and a full benchmark table. The official announcement on X(opens in new tab) established a firm timebox:

  • Open weights for Qwen3.8-Max — the full 2.4T-parameter, ~95B-active MoE model — land on Hugging Face and ModelScope during the week of August 10.
  • Qwen3.8-27B — a dense 27-billion-parameter companion — goes open-weight at the same time. This is the artifact most developers can actually run on local hardware.
  • The hosted API is live on QwenCloud at $2/$6 per 1M tokens (input/output) with $0.25 cached input, and a 1M-token context window.

As of Monday, August 10, the Qwen HuggingFace organization page contains no matching repository, no weight files, and no license file. The only specific date — August 12 — comes from X user @hqmank(opens in new tab), not from Alibaba. The official window runs through August 16.

Alibaba published the following benchmark numbers with the August 3 launch. All figures are vendor-claimed — not independently reproduced.

BenchmarkQwen3.8-MaxGPT-5.6 Sol MaxFable 5
Terminal-Bench 2.186.688.884.6
OSWorld-Verified86.182.7
SWE-bench Pro67.780.0
FrontierSWE73.588.8

The 16-day autonomous coding run and 5-day research reproduction that Alibaba showcased alongside these numbers are vendor demonstrations, not third-party audits.

What's still missing: license, files, benchmarks, runtime support

As of August 10, 2026, none of the following are known:

WhatStatus
Actual weight filesNot on Hugging Face or ModelScope
LicenseUndisclosed — Qwen3.6 used Apache 2.0, but that is precedent, not a commitment
27B architectureNo context window, benchmark, or architecture details published
Runtime supportNo deployment guide; serving stacks (vLLM, SGLang) need a reference implementation
Quantized buildsCommunity quants follow runtime support, which follows the release — days to weeks behind
Delivery dateAug 12 is a secondary-source rumor, not an official Alibaba statement

Digital Applied(opens in new tab) puts it bluntly: "A dated commitment is not a download." Alibaba's revenue-share announcement for large Qwen3.8-Max API users — reported alongside the launch — signals that the commercial terms around this model are evolving. Read the LICENSE file before downloading, not the launch tweet.

Why the 27B companion matters more than the 2.4T flagship

This release — if it lands — closes a structural gap in the open-weight frontier. The Qwen Max line has been API-only since its inception. Opening it signals that Alibaba is betting on ecosystem adoption over exclusivity, the same play DeepSeek and Moonshot ran before them.

But the 27B dense companion is arguably the bigger deal for most developers. A 2.4T MoE requires datacenter-scale hardware — all 2.4T weights must be resident in memory reachable by the accelerator, even though only ~95B activate per token. The 27B fits on a single high-end GPU or an Apple Silicon Max machine, in the same bracket as other 2026 open-weight models at that scale. On r/LocalLLaMA, the 27B generated more excitement than the 2.4T flagship.

For developers, the calculus is split:

  • Self-hosters get frontier-class capability without per-token fees or data-jurisdiction concerns — but only if they have the hardware to serve a 2.4T MoE. For most teams, that means a multi-node GPU cluster.
  • API users already have access at $2/$6 per 1M tokens — less than a third of Claude Opus 5's $30 and under a quarter of GPT-5.6 Sol Standard's $35. The open weights don't change that math today.
  • 27B users get the most practical artifact: a model that runs on consumer hardware and is likely competitive with other 2026 open-weight models in its class.

For the directory: Qwen3.8-Max remains pending. Open weights are a necessary but not sufficient condition for a recommendation. We need independent benchmarks — not Alibaba's self-reported numbers — a disclosed license, and evidence the model performs at the level claimed when deployed outside Alibaba's infrastructure.

What changes for you

  • Monitor the Qwen HuggingFace organization page this week. The week-of-August-10 window runs through August 16. Check daily — but do not block your sprint on an undelivered artifact.
  • Read the LICENSE file before downloading or integrating into any project. Alibaba's revenue-share model for large API users suggests the commercial terms are in flux. Apache 2.0 is precedent from Qwen3.6, not a commitment for 3.8.
  • Target the 27B for local deployment experiments. The 2.4T MoE requires multi-node GPU clusters; the 27B fits on a single high-end GPU or Apple Silicon machine.
  • Wait for independent benchmarks before evaluating quality. Alibaba's self-reported numbers on Terminal-Bench, OSWorld, and SWE-bench are vendor claims — not third-party audits.
  • If you need a production model today, use Qwen3.6-27B, Gemma 4, or Kimi K3 — all have shipped, verified weights with clear licenses.

FAQ: delivery dates, hardware requirements, and license unknowns

Will the weights actually drop on August 12? The August 12 date comes exclusively from X user @hqmank(opens in new tab), not from Alibaba. The official commitment is "the week of August 10." That window runs through August 16. If the date is real, expect a Hugging Face repository on Tuesday. If not, the window is still open — and Alibaba has never shipped open weights for a Max-class model before, so there is no delivery track record to lean on.

Can I run a 2.4T MoE on my own hardware? Not without a datacenter. Although MoE architectures activate only ~95B parameters per token, all 2.4T weights must be resident in GPU-addressable memory. The 27B companion is the artifact designed for local deployment on a single high-end GPU.

What license should I expect? Unknown. Qwen3.6-27B carried Apache 2.0, but Alibaba's revenue-share model for large API users suggests the commercial terms are in flux. Do not assume Apache 2.0. Read the LICENSE file before integrating.

Is the directory verdict changing? No. The model stays pending. Open weights are a milestone, not a recommendation. We require independent benchmarks, a disclosed license, and real-world deployment performance data before we can rate it.

Are the benchmarks verified? No. The benchmark numbers in the table above come from Alibaba's August 3 launch post and have not been independently reproduced. The 16-day autonomous coding run and 5-day research reproduction are vendor demonstrations, not third-party audits.

What to do

  1. 1 Wait for the LICENSE file before downloading or integrating into any project
  2. 2 Target the 27B for local deployment experiments — the 2.4T MoE requires multi-node GPU clusters
  3. 3 Monitor the Qwen HuggingFace organization page this week for weight files

Affected tools & models

Never need to catch up again

The weekly delta — only verdict changes and act-now items. No digest filler.

By subscribing you agree to our Privacy Policy. Unsubscribe anytime.