What is genuinely new in 3.8

The official Qwen card describes Qwen3.8-27B as the successor to Qwen3.6-27B and the most capable generation of the open Qwen family so far. It is dense, not a mixture of experts: 64 layers in sixteen cycles of three Gated DeltaNet blocks plus one full-attention block, 24 query heads, four KV heads, a 17,408-wide FFN. The architecture tag in the config says qwen3_5 — the card is explicit that 3.8 sits on the Qwen3.5 foundation. The genuinely new bits for this size class: a 27-layer vision encoder, multi-token prediction (MTP), per-request reasoning_effort, and a 262,144-token native context that Qwen says extends to a million via static YaRN.

The exact Huihui artifact contains 27,781,427,952 BF16 parameters across 18 shards, roughly 55.6 GB according to the Hugging Face model API. At the time of writing the API reports 1,485 downloads and 82 likes. The edit details below trace to the model card or the pinned configuration.

The 48-hour race, with timestamps

Qwen launched Qwen3.8-Max on 3 August 2026 and promised the 27B open weights “next week” in the release article. The upstream repository appeared on Hugging Face on 5 August, but the artifacts the community could actually download — judging by the official FP8 release and the first unsloth quantizations, both timestamped 13 August — arrived around 13–14 August, with community countdowns aimed at a 15 August midnight. From that community “release” moment, huihui-ai’s edit at 08:22 UTC on 16 August is inside 48 hours. From the 13 August quant wave, about 72.

The minutes after publication tell the rest of the story. A discussion asking for a GGUF format opened at 10:26 UTC; huihui-ai pushed the GGUF companion repository at 13:18 UTC with twelve quantizations plus BF16 and an mmproj vision projector; a “Tests” thread and then a “Fantastic model! We would like to serve this model for free” thread followed within a day, and the account announced both repositories on X. That cadence matters: the edit, the quants and the community plumbing all landed inside one working day.

What the edit actually touched

The card’s note is unusually specific: the first 15 layers were retained without ablation, and MTP and the visual encoder were not modified. Of the 64 text layers, 49 were projected; the vision tower and MTP head were never part of the operation. The card also calls the work a “crude, proof-of-concept implementation” using Sumandora’s pure-Transformers approach rather than TransformerLens — the same refusal-direction family as Arditi and colleagues’ original paper. No refusal-rate benchmark and no post-edit rerun accompany the release.

What is proven here?

The artifact, the shard layout and the edit’s boundaries are inspectable. The upstream benchmark suite is published. That the derivative is refusal-reduced is a publisher claim, and the untouched vision tower means multimodal behavior was neither re-ablated nor re-evaluated.

Upstream numbers, upstream only

Qwen’s own card claims 73.0 on Terminal Bench 2.1 (Terminus), 61.7 on SWE-bench Pro, 42.2 on DeepSWE 1.1, 79.0 on QwenSWEBench, 89.2 on GPQA Diamond, 30.8 on HLE and 90.3 on LiveCodeBench v6, plus multimodal results like 84.3 on OSWorld-Verified and 94.6 on MathVision with chain-of-thought. Those are upstream claims about Qwen’s checkpoint, evaluated with the harnesses and footnotes on the official card. Huihui publishes no corresponding rerun after weight editing. The interesting question is not whether the upstream model is strong — the numbers say it is — but how much survives this particular projection.

The variant wave: what is actually useful

The model tree on the Huihui page lists 108 models built on Qwen3.8-27B, and a Hugging Face search for the name returns over a hundred repositories inside a week: GGUF from unsloth (2.7 million downloads), NVFP4, MLX 4-bit and 8-bit from mlx-community, AWQ and AutoRound INT4, FP8 from Qwen itself, exl3, and MTP-tagged variants of most of those. Practical guidance: huihui’s own GGUF is the default local path — the card ships an Ollama one-liner, and the Ollama page lists an 18 GB build with a 256K context and image support. NVFP4 suits Blackwell-era NVIDIA hardware; MLX suits Apple Silicon; the “MTP” suffix only matters if your engine exploits multi-token prediction. One honest caveat: most of the other “abliterated” 27B repositories are independent edits of the base model, not forks of huihui-ai’s — its model tree shows a single merge downstream.

How to run it

The easiest local path is the Ollama library page: an 18 GB build, 256K context, text and image input, one command:

ollama run huihui_ai/Qwen3.8-abliterated

The GGUF companion repository ships twelve quantizations plus BF16 and an mmproj vision projector, so llama.cpp, LM Studio and MLX all work. For a server, vLLM serves the exact Hugging Face repository directly, and the OpenAI-compatible endpoint here on ABLITERATED.cloud uses the same pinned revision — request access and it costs an estimated $5.45/hour on one H200, scale-to-zero included.

Community temperature

The discussion threads are the primary community record: the GGUF request, the test thread, and a third offering free serving. An r/LocalLLaMA thread titled “Huihui-ai Qwen 3.8 Ablit Available” exists, but Reddit’s API returned 403 to our tooling, so we flag it as a coverage gap rather than paraphrase it. Videos calling the 27B “basically Opus-level” are community opinion, not measurement.

The creator: huihui.ai

The Qwen team built the architecture and trained the base model. The person you actually owe for this checkpoint is the operator behind the huihui-ai handle — huihui.ai — whose profile describes work on model ablations and collaboration with the open-source NLP community, and who maintains more than 180 model repositories. This is a one-person-scale operation, not a lab: PRO user, “Open to Work”, and a release cadence that no team matches. When Qwen dropped the 3.8-27B weights, huihui.ai had an abliterated edit public inside 48 hours and the GGUF ladder up the same afternoon, then announced both on X. That is the fastest refusal-reduction pipeline in the open ecosystem, and it runs on coffee and donations.

The Qwen3.8 abliterated collection gathers the family. Model updates go out on X at @support_huihui, and the card is refreshingly direct about funding: “a cup of coffee can do it” — Ko-fi (ko-fi.com/huihuiai) or Bitcoin bc1qqnkhuchxw0zqjh2ku3lu4hq45hc6gy84uk70ge. If you've run anything from huihui.ai, you've almost certainly never paid a cent for it. That is the entire model.

How we treat it

Our prepared profile pins the revision above, serves a conservative 131,072-token context on one H200 at an approximate managed price estimate of $5.45/hour, and does not transfer Qwen’s benchmarks to our endpoint until the exact artifact and runtime are measured. The card says safety filtering is significantly reduced — which is the whole point of this one. “Abliterated” means refusal-reduced, and what you do with that is your call.

The idea, in plain words

Predicting several words at once

Most models predict one next token, then the next. Qwen3.8 adds multi-token prediction (MTP): it guesses several tokens ahead in one step, which speeds generation and nudges quality up. Its Gated DeltaNet layers are a cheaper form of attention that keeps a compact memory of what came before — part of why the 3.8 generation feels faster for the same size.

Primary sources