Models · · 2 min read

Qwen 3.7 open-weight watch — what is confirmed, what is still rumor, what to actually do now

Qwen 3.7-Max launched on the API two days ago, but the open-weight release the local-LLM crowd is waiting for has no announced date. Here is what is actually known, what is reasonable to project from Alibaba's past cadence, and what to run right now.

Two days after Qwen 3.7-Max landed on the API, the loudest question on r/LocalLLaMA and the Qwen GitHub issues isn’t “is it good” — it’s “when can I download it and run it on my own hardware?”

Short answer as of May 22, 2026: nobody outside Alibaba knows for sure, and the GitHub evidence is unambiguous. Here’s the Qwen org’s Pinned repos right now:

GitHub QwenLM organization Pinned repositories showing Qwen3.6, Qwen3-VL, Qwen3-Coder, Qwen3-Omni, Qwen-Agent, Qwen-Image — no Qwen 3.7 repo
The Qwen GitHub organization's Pinned repos on May 22, 2026. Qwen3.6 is the latest open-weight family. No Qwen 3.7 repo exists yet. Source: github.com/QwenLM

What’s confirmed

  • Qwen 3.7-Max API: live on Alibaba Cloud Model Studio / DashScope since May 20-21, 2026 — see our Qwen 3.7-Max walkthrough for the real screenshots and how to use it via the free Qwen Chat
  • Max stays proprietary: per Alibaba’s release patterns and third-party reporting, the flagship Max variant is API-only. Smaller variants are what historically get open-weighted
  • Apache 2.0 is Alibaba’s consistent open-weight license — Qwen 3.5-27B, Qwen 3.6-35B-A3B (MoE), and Qwen 3.6-27B (dense) all shipped under Apache 2.0

What’s a reasonable projection (not confirmed)

Alibaba’s pattern for the Qwen 3.6 family was: API first, open weights about 3 weeks later.

MilestoneQwen 3.6 (last cycle)Qwen 3.7 (this cycle, projected)
API launchLate March 2026May 20-21, 2026 ← confirmed
First open-weight (MoE)April 17, 2026 (~3 weeks later)~mid June 2026 (projected)
Dense variant follow-upApril 23, 2026 (+6 days)~late June 2026 (projected)

These are projections, not promises. Alibaba has published no Qwen 3.7 open-weight timeline. If the cadence breaks (either way), the projection above is wrong. Don’t commit production migrations to it.

What’s pure speculation right now

  • Specific parameter counts (community guesses range from “another 35B MoE” to “70B dense” — none confirmed)
  • HuggingFace repo URLs (no Qwen/Qwen3.7-* placeholder has been created)
  • Whether a smaller (sub-10B) variant will ship for laptop / Mac unified memory
  • Whether Qwen 3.7 will require new tokenizer / inference-stack changes vs Qwen 3.6

What to actually do right now

Three options ordered by pragmatism:

  1. Run Qwen 3.6-35B-A3B (MoE) locally today. It’s already on HuggingFace, Apache 2.0, runs in ~21GB VRAM at Q4. It’s not 3.7 but it’s what’s available, and the agentic workflow improvements Alibaba shipped in 3.7 mostly require the API anyway (Max-only).
  2. Use Qwen 3.7-Max via API now for the agent-frontier capability. $1-3 per million tokens (final pricing not yet posted on DashScope); test via chat.qwen.ai free first.
  3. Watch the Qwen GitHub org weekly. A new top-level Qwen3.7 repo appearing is the unambiguous signal that an open-weight release is imminent. Subscribe to GitHub releases on github.com/QwenLM/Qwen3.6 — the next major bump there often telegraphs the new family.

For builders deciding between locking in on Claude Haiku 4.5 (closed, API-only) vs Qwen 3.7 (closed Max API today, but a future open variant): see our Gemini 3.5 Flash vs Claude Haiku 4.5 comparison for the frame, then add Qwen as “Apache-2.0-licensed-eventually” — which is a real differentiator if your stack needs self-hosting.

Sources

Source: Qwen GitHub org