Skip to main content

ClovisChat - Qwen3.8-Flash-Next

· 13 min read
Basile Chevalier
Basile Chevalier
Project manager

ClovisChat will move to Qwen3.8-Flash-Next, replacing Qwen3.6-35B as its conversation and vision model. The ClovisChat alias will remain unchanged: this transition only affects the underlying model.

[object Object]

Technology-themed banner showing the transition from Qwen3.6 to Qwen3.8, with the model icon in the center.

Qwen3.6
Previous version
› › ›
› › ›
Qwen3.8
Flash-Next

This transition aims to improve everyday assistance: understanding a request, reasoning through a problem, and supporting work across multiple steps.

Key figures​

ClovisChat currently uses Qwen3.6-35B. The charts compare the official scores for Qwen3.6-35B with those for Qwen3.8-Flash-Next.

The figures come from the official model cards for Qwen3.6-35B-A3B and Qwen3.8-Flash-Next.

Qwen3.6-35B-A3BQwen3.8-Flash-Next

GPQA Diamond — Scientific reasoning — +5.7 points

86.0
91.7

HLE — Multidisciplinary reasoning — +14.5 points

21.4
35.9

LiveCodeBench v6 — Solving programming problems — +11.5 points

80.4
91.9

RealWorldQA — Real-world visual understanding — +3.2 points

85.3
88.5

These scores are technical indicators. They do not directly measure the quality of a conversation in French or ClovisChat’s response time.

Why some gains are much larger than others​

The reported gap is larger on HLE than on RealWorldQA. These tests assess different skills: multidisciplinary reasoning and image understanding. This evolution therefore cannot be summed up as a single percentage improvement.

For ClovisChat, the priority use cases to evaluate are:

understanding a request with multiple constraints
structuring an actionable response
reasoning through a complex problem
interpreting a provided image
following the thread of a conversation
using the available tools appropriately

Comparison with other models​

The table published alongside Flash-Next also shows how the model compares with other reference models:

BenchmarkQwen3.8-Flash-NextQwen3.7-PlusDeepSeek-V4-Flash-0731Claude Opus 4.6 (Max)
GPQA Diamond91.790.390.891.3
HLE35.934.733.840.0
LiveCodeBench v691.989.690.688.8

Flash-Next leads this selection on two benchmarks; Opus retains the advantage on HLE. This table is not an overall ranking. Source: official Qwen evaluations.

Practical improvements in software development​

Qwen3.6-35B-A3B scores 49.5 on SWE-bench Pro, using an in-house agent and a 200K-token context window. Source: Qwen3.6-35B-A3B.

Flash-Next reaches 62.5, using Claude Code and a 256K-token context window. Because the evaluation setup changed, the gap does not measure improvements in the model alone. Source: Qwen3.8-Flash-Next evaluation setup.

In a coding conversation, the intended benefits include:

explaining a code snippet
spotting an inconsistency
suggesting a fix and explaining it
respecting project constraints
suggesting useful checks
revising a solution based on user feedback

A new architecture designed for efficiency​

Flash-Next previews the architecture of Qwen4. Its main model has 125 billion parameters, with 6 billion activated per token, plus 51 billion N-gram embedding parameters. These figures describe different components, so 125 billion does not account for all the weights. Source: official Qwen repository.

In ClovisChat, the maximum context window is set to 262,144 tokens, including both input and output. A response can contain up to 32K tokens; when this full output capacity is reserved, approximately 230K tokens remain available for the prompt, conversation history, and provided documents.

The attention mechanism combines Gated DeltaNet with Qwen Sparse Attention, which selects relevant context blocks. Gated residual connections improve information flow between layers, while N-gram embeddings add capacity with little extra computation. The goal is to use resources more efficiently, particularly for long sequences. Source: Qwen technical report.

What Qwen3.8-Flash-Next does not solve​

A higher score does not guarantee that any given answer is correct. Factual answers, suggested code, and actions performed with tools must remain verifiable.

For professional use, the same best practices still apply:

  • check critical information against its sources;
  • test code before integrating it;
  • limit tool permissions to what is needed;
  • retain human approval for critical operations.
Update made by
Basile ChevalierBasile Chevalier