> Lineage: Qwen3.8-27B post-training derivative | by UkisAI | cross-verified via eight search routes, official benchmark page, and the author's HN write-up
Bottom line first. This model treats a very specific disease: Qwen3.8-27B thinks too much. Thinking tokens cut 58.3%, average accuracy drops under 1%, throughput up 1.95x. The numbers have some measurement caveats, but the disease is real and the medicine fits. The most valuable part isn't the result — it's the author's publicly documented trial-and-error process on HN, including one clean failure.
1. What This Model Is
A post-training version of Qwen3.8-27B from UkisAI. Not coarse full-weight fine-tuning, but targeted surgery on "overthinking tokens." Released as an adapter to be mounted on the original Qwen3.8-27B. Text, image, and video capabilities all preserved.
The motivation was practical: the author's own quantized Qwen3.8-27B instance kept falling into random reasoning loops — repeating the same checks, still thinking after the answer was obvious. Neither medium nor low reasoning_effort fixed it.
2. Method: Five Steps, One Died
The author laid out the full pipeline on HN, in order:
1. Found a Meta paper (arXiv:2606.00206) on overthinking mitigation for PTQ scenarios. Out-of-the-box results were mediocre. 2. Used 8×H100 to generate large amounts of out-of-distribution traces across four domains: coding, language, vision, agentic. 3. Grouped traces containing overthinking and extracted common tokens. 4. Built an inference-time penalizer from those tokens. 5. Planned to generate clean traces with the penalizer, then SFT them into weights via cross-entropy.
Step five completely failed. The author's words: "Did not work at all."
But something was salvaged: the penalizer itself works better than the Meta paper's tokens, and it works on BF16 too, not just low-precision models. The final product combines the penalizer idea with a transfer component from BottleCap AI's ThinkingCap-Qwen3.6-27B, a predecessor in the same niche.
This failure deserves its own note: inference-time penalization works, distilling into weights dies — suggesting "thinking less" is anchored at the level of inference dynamics, not the static distribution. The penalizer is an external brake; SFT tried to weld the brake in, and it won't weld.
3. The Ledger and Its Caveats
Nine benchmarks, BF16, five runs per model, averaged. Key rows:
| Benchmark | Accuracy change | Mean thinking-token reduction | |------|---------|-------------------| | GPQA-Diamond | 88.38 → 88.28 | -41.0% | | C-Eval | 90.00 → 90.62 | -46.1% | | AIME 2026 | 98.67 → 94.00 | -26.7% | | HMMT Nov | 99.33 → 96.00 | -31.1% | | LiveCodeBench v6 | 76.76 → 81.55 | -24.3% | | Terminal-Bench 2.1 | 66.74 → 65.84 | -38.7% |
A few conclusions from the customs inspection:
The headline number is a median. The 58.3% refers to GPQA's median reduction — the largest in the whole suite. Mean is only 41%. The official page states this itself, and notes LiveCodeBench measures completion tokens while other rows measure thinking tokens. A vendor breaking down the headline number's methodology on its own launch page is above community-average honesty. Credit given.
"No average accuracy loss" hides hard-math losses. AIME drops 4.67 points, HMMT drops 3.33. Competition-level difficulty pays with thinking length. Code actually gains 4.79 points, and Terminal-Bench's four-hour long tasks are nearly unscathed. The cost of thinking less is uneven — math eats the budget, code and long-horizon tasks don't.
Some baseline outputs reused archived runs. For reproduction, request their harness manifests. Small deduction.
4. The Most Interesting Control: Quantization and Accuracy Loss Canceling Out
The official page also tested quantized variants. Under W4A16 mixed precision and AWQ INT4, token savings fully carry over. The surprise was AIME:
At BF16, Swift loses 4.67 points. At INT4, base scores 82.67 and Swift 84.00 — a 1.33-point reversal.
Two taxes canceled each other. Quantization knocked 14 points off the floor; Swift's 4.67-point thinking cut was drowned in quantization noise, and may even net-gain from fewer reasoning loops. This non-monotonic phenomenon is the most valuable experiment in the piece.
Follow the thread one layer deeper. Swift's motivation was precisely "reasoning loops on quantized instances." An HN commenter offered a hypothesis: low-quantization models lack confidence in their own reasoning, hence more overthinking. Unverified, but the direction is right — quantization tax has a behavioral face. Quantization discussions used to only count accuracy points; now there's another dimension: quantization changes thinking behavior, not just scores. Score loss is a static tax; induced overthinking is a dynamic tax — and the dynamic tax carries interest (thinking tokens cost money too).
5. The Landscape: Three Intervention Layers
There are three layers of attack on overthinking, classified by intervention point:
| Layer | Representative | Cost | Effect | |----|------|------|------| | Template | Qwen-Sharp-Chat-Templates, chat_template edits encouraging brevity | Zero training, swap a jinja file | Mild | | Interface | Official reasoning_effort parameter (medium/low) | Zero cost | Native, but Swift saves another 22–25% at the same setting | | Weights | Swift, ThinkingCap | 8×H100-class training | ~58% compression, stackable with the other two |
Swift keeps saving tokens under medium and low effort settings, showing weight-level surgery and interface-level parameters act independently and don't conflict. All three layers stack.
The same niche also includes BottleCap's ThinkingCap (Qwen3.6 era, best-case 90% mean reduction) and community quantization practices on Reddit. "Short thinking" went from paper topic to product track within these two months.
6. Three Independent Observations
Observation one: this is a contrarian bet against the test-time compute arms race. The whole industry is adding thinking budget; this line subtracts. Same bet direction as Jev's judgment models: not every scenario deserves longer thinking. The evidence is isomorphic — Terminal-Bench long tasks losing almost nothing shows most scenarios' thinking budgets are waste; AIME dropping shows competition scenarios aren't. The value of thinking budget is task-dependent, and someone has started mapping that curve.
Observation two: the scratchpad problem gains a fifth solution. Four were previously recorded: discard-level (Prefix Sliding, dropping the window), window-level, latent-space-level (latent reasoning, scratch never materialized as tokens), and fixed-point-iteration-level (DBTM adaptive). Swift is behavior-level — the scratchpad is still written, but training makes it shorter. Structure untouched, interface untouched, behavior changed. Laid side by side, five solutions show "the cost of intermediate thinking" is a multi-dimensional optimization problem, with someone working every dimension.
Observation three: the MTP mainline isn't broken. The community quantization chain has already produced suzu89/Swift-Qwen3.8-27b-oQ8-mtp, an MLX build carrying MTP. A previous dissection of the Qwen3.8 launch's 72-hour quantization ecosystem noted MTP fidelity as the community's dividing line; that chain continues in Swift. Also, mradermacher's Abliterated (uncensored) version is out, meaning the distribution chain has entered phase two — no longer curiosity, people are using it as a daily tool.
7. Falsifiable Predictions
Within 12 months, short thinking goes from community derivative to official product line: Qwen or a peer vendor ships a weight-level short-thinking variant, or makes thinking-budget training a configurable switch. Rationale: overthinking is independently confirmed as a trainable dimension by multiple parties, interface-level effort parameters landed first, and weight-level consolidation is step two — every GPU generation gets more expensive, and the thinking-token bill will eventually reach the vendors.
Second prediction: short-thinking models' accuracy loss will amplify in ultra-long thinking budget scenarios. With the thinking scaling curve flattened, the marginal returns at xhigh will plateau earlier than base. Whoever first measures that curve's inflection point gets the next post.
---
*Key references: ukisai.com/news/introducing-swift (official benchmark page), HN Show HN 49727511 (author's methodology), bottlecapai.com ThinkingCap launch page, arXiv:2606.00206 (Meta PTQ overthinking), HuggingFace ukisai/Swift-Qwen3.8-27B-GGUF, r/LocalLLaMA third-party comparison thread.*