Qwen4-Max
- ID
- 46900
- Status
- summarized
- Published
- 16 Nov 2026, 10:14 AM
- Fetched
- 16 Nov 2026, 2:09 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://qwen.ai/blog?id=qwen4-max
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 16 Nov 2026, 2:10 PM
- Tags
- Audience
- developersai_ml_learnersai_agent_userssaas_founders
What happened
Qwen released Qwen4-Max, a model on a new Qwen4 architecture with a 2.4-trillion-parameter backbone, native vision, and a one-million-token context window. The vendor reports token-usage cuts versus Qwen3.8-Max of roughly 24%/35% on its Work360 eval and 48%/49% on Terminal-Bench 4.0, plus lower API prices with large reductions in cached-input pricing — average cost per Work360 task falling from $4.43 to $1.67, a 62% drop. The Hacker News thread drew 285 points and 94 comments; all performance and cost figures in the post are vendor-run evaluations.
Why it matters
The only hard, checkable numbers here are the price and token-efficiency claims: $4.43 to $1.67 per task and ~48-49% fewer tokens on Terminal-Bench 4.0. If you run high-volume agent or coding workloads, that is a concrete reason to re-run your own eval suite on Qwen4-Max and compare against your current model — especially cached-input pricing, since prompt-cache-heavy agent loops are where the biggest cut is claimed. Do not migrate on the vendor's chart alone; the post gives no independent benchmarks and the performance comparison is self-reported.
Discussion angle
Take one agent task your team actually ships, run it on Qwen4-Max and your current model, and compare real cost-per-completed-task against the claimed $1.67 — what would Qwen have to show for you to switch routing?