Alibaba’s Qwen team announced Qwen3.8-Max, a 2.4-trillion-parameter mixture-of-experts model with about 95 billion parameters active per step, aimed at coding, research, and long-horizon agentic work. Qwen says this will be its first Max-class model released with open weights and plans to publish those weights the following week, including support for third-party coding-agent environments. The supplied results do not yet establish practical self-hosting requirements, independent coding performance, successful quantizations, or the claimed Call of Duty clone beyond a referenced demonstration.
Scott already holds the decisive position in “Usable Mass Over Unusable Power”: nominally powerful open weights matter only when serving cost, latency, quantization fidelity, and harness performance make them deployable. This new release could affect his hardware-aware local-inference and coding-agent experiments, but its practical significance remains contingent on the same independent validation already tracked in the Krasis, Slipstream, and large-model quantization radar cases.
ip:concept.usable-mass-over-unusable-powerip:concept.model-plus-harness-benchmark-unitip:concept.capability-auditdev:concept.hardware-aware-local-inferencedev:project.askradar:concept.open-modelsradar:concept.moe-inferenceradar:concept.quantizationradar:concept.coding-agent-benchmarksradar:krasis-single-gpu-ornith-397bradar:slipstream-ssd-moe-streamingradar:hy3-one-bit-quantization
queries asked of Scott's wikis
- open weights and model sovereignty
- local inference economics for giant MoE models
- quantization effects on coding-agent capability
- self-hosted models in coding-agent harnesses
- independent evals versus vendor coding demos
- serving constraints for open frontier models
2026-09-03T06:26:57Z
The expected release-and-validation window has passed without a verifiable weight artifact, reproducible evaluation, serving evidence, or quantization implementation. This specific episode has faded; any later substantive artifact should open a fresh case rather than keep this dormant watch alive.
2026-09-01T05:38:02Z
The staleness trigger adds no artifact, independent evaluation, serving economics, or quantization implementation, so the case remains a dormant validation watch. Recheck only on a weekly cadence or when substantive downstream evidence appears.
2026-08-30T05:29:44Z
This check adds only immaterial engagement drift and no released-weight artifact, reproducible evaluation, serving economics, or quantization implementation. The practical-validation hypothesis remains open but dormant and should stay on a weekly artifact-driven cadence.
2026-08-28T05:24:50Z
Another staleness trigger adds only immaterial engagement drift, with no released-weight artifact, reproducible evaluation, serving-cost evidence, or quantization implementation. Keep the validation watch open but move it to a weekly cadence unless a substantive artifact appears.
2026-08-26T04:33:25Z
Another staleness check adds no first-party weight artifact, reproducible evaluation, serving-cost evidence, or quantization implementation. The case remains dormant but open because the announced release and downstream validation window has not yet clearly closed.
2026-08-24T04:27:24Z
The staleness check adds no artifact, independent evaluation, serving-cost evidence, or quantization implementation; the single extra reaction is immaterial. Keep the case dormant until first-party weights or substantive downstream deployment evidence appears.
2026-08-22T04:26:42Z
The 48-hour staleness trigger brings no new artifact, reproducible evaluation, serving-cost evidence, or quantization implementation. The case remains a low-temperature validation watch rather than an established practical open-model development.
2026-08-20T03:27:39Z
The comparison link indicates tentative downstream interest but exposes no methodology, results, reproducible artifact, serving economics, or quantization work. It therefore does not yet provide the independent validation needed to advance the case.
2026-08-20T03:22:32Z
evidence attached: hn.story.49369831 — An independent UI comparison provides downstream evidence about Qwen3.8 Max's practical capability relative to Fable 5.
2026-08-19T12:33:57Z
The refreshed comments remain repetitive reactions to the same unverified demonstration and add no released-weight artifact, reproducible prompt, independent evaluation, serving-cost disclosure, or quantization result. The case still depends on first-party artifacts and substantive downstream implementation.
2026-08-19T11:30:33Z
The refreshed comments remain reactions to the same unverified demonstration and add no released-weight artifact, reproducible run, independent evaluation, serving-cost evidence, or quantization implementation. The case remains a speculative validation watch pending first-party artifacts or substantive downstream testing.
2026-08-19T07:33:07Z
The refreshed comments are repetitive reactions to the same unverified demonstration and add no first-party weights, reproducible run, independent evaluation, serving-cost evidence, or quantization work. The case remains a speculative validation watch pending an artifact or substantive downstream implementation.
2026-08-19T06:37:05Z
The refreshed comments remain reactions to the same unverified demonstration and provide no first-party weights, reproducible run, cost disclosure, independent evaluation, or quantization work. The case remains a speculative validation watch and should wait for an artifact or substantive downstream implementation.
2026-08-19T04:31:51Z
Refreshed comments remain reactions to the same unverified demonstration and add no first-party weights, reproducible run, independent evaluation, serving-cost data, or quantization implementation. The case remains a speculative validation watch, and repetitive discussion no longer merits hourly review.
2026-08-19T02:30:15Z
The refreshed discussion adds no first-party artifact, reproducible run, independent evaluation, serving-cost evidence, or quantization implementation. The case remains a speculative validation watch pending released weights or substantive downstream testing.
2026-08-19T01:25:19Z
The refreshed comments are further amplification of the same unverified demo, not independent evidence of released weights, reproducible coding performance, serving economics, or quantization progress. The case remains a speculative validation watch pending a first-party artifact or substantive downstream implementation.
2026-08-19T00:25:05Z
The refreshed comments remain repetitive reactions to the same unverified demo and add no first-party artifact, reproducible run, independent evaluation, serving-cost evidence, or quantization implementation. The case still hinges on the promised weight release and substantive downstream validation.
2026-08-18T23:44:49Z
The refreshed comments add no artifact, independent testing, reproducible run details, serving economics, or quantization work. This remains a speculative validation watch until first-party weights or a substantive downstream implementation appears.
2026-08-18T22:38:01Z
The refreshed discussion remains repetitive commentary on the same unverified demo, with no first-party artifact, reproducible prompt/run, cost disclosure, independent benchmark, or quantization progress. Its meaning is unchanged: a speculative validation watch pending released weights and substantive downstream implementation.
2026-08-18T21:38:02Z
The refreshed comments remain repetitive reactions to the same unverified demo and add no artifact, independent test, serving-cost data, or quantization implementation. The case still hinges on first-party weights and substantive downstream validation.
2026-08-18T20:39:08Z
Refreshed comments sharpen skepticism about controllability, output quality, and cluster cost but add no independent artifact, benchmark, quantization, or reproducibility evidence. The case remains a low-temperature validation watch pending first-party weights or substantive downstream implementation.
2026-08-18T18:59:07Z
The refreshed discussion adds attention but no independent confirmation of released weights, reproducible coding capability, serving economics, or quantization progress. The case remains a speculative validation watch and can cool until a first-party artifact or downstream implementation appears.
2026-08-18T18:32:03Z
grounded: known/medium — Scott already holds the decisive position in “Usable Mass Over Unusable Power”: nominally powerful open weights matter only when serving cost, latency, quantiza
2026-08-18T18:26:18Z
case created — The reported open-weight release and large-scale coding run create a concrete model-validation and quantization episode distinct from the existing Qwen3.8-27B cases.