This is a simplified guide to an AI model called Qwen3.8-Flash-Next maintained by Qwen. If you like these kinds of analysis, you should join AImodels.fyi or follow us on Twitter. Overview Qwen3.8-Flash-Next is an experimental open-weight causal language model with a vision encoder from Qwen. It targets coding agents, long-horizon tool use, multimodal computer tasks, multilingual software engineering, and reasoning. The most important point before adoption is that this is an architecture preview intended to underpin Qwen4, not the production-hosted Qwen3.8-Flash service: the hosted version adds production features such as 1M-token context by default and official built-in tools. The model has 125B total language-model parameters with 6B activated, plus 51B n-gram embedding parameters and 4B multi-token-prediction parameters. It provides 262,144 native context tokens and can extend to 1,000,000 tokens. The repository supplies post-trained weights and configuration in Hugging Face Transformers format, with compatibility listed for Transformers, vLLM, SGLang, TokenSpeed, and other serving systems. The model card lists the license as other; it does not provide terms that establish commercial-use rights, so legal review is required before commercial deployment. Best use cases Long-horizon coding agents. The model suits repository-level coding, debugging, test execution, and tool-driven software work. It scores 62.5 on SWE-bench Pro, 81.0 on SWE-bench Multilingual, 58.7 on DeepSWE 1.1, and 91.9 on LiveCodeBench v6. Its 256K evaluation context, sparse attention design, multi-step training, and agent-oriented post-training support workflows that require reading large repositories, planning changes, invoking tools, and recovering from failures. Multilingual software engineering. Choose it for coding tasks across multiple programming-language and natural-language environments. Its 81.0 SWE-bench Multilingual score exceeds the listed results for Qwen3.8-27B at 73.8 and Qwen3.7-Plus at 75.8. The model’s general instruction-following score of 81.3 and competitive-coding score of 91.9 also support structured implementation and problem-solving tasks. Tool-using productivity agents. The model performs well on office and professional workflows that require multiple actions rather than a single answer. It scores 73.9 on CoWorkBench, 55.7 on JobBench, 51.2 on Agents’ Last Exam, and 73.5 on Toolathlon Verified. These results make it a candidate for research assistants, document workflows, finance or legal task automation, and other systems that combine reasoning with external tools. The model card warns that reducing reasoning effort can lower total completion time in multi-turn agents by causing failures and retries, so per-turn latency is not the only performance metric. Multimodal computer-use systems. The vision encoder and multimodal benchmark results support tasks such as navigating Android applications, recreating applications across desktop, mobile, and web platforms, analyzing charts, and solving visual mathematics. It scores 84.5 on AndroidWorld, 19.4 binary and 52.3 partial on OSWorld 2.0, 49.9 on RecreationBench, 64.0 on Vision2Web, and 88.5 on RealWorldQA. These results favor research systems that connect screenshots or visual documents to actions and structured responses. Scientific and visual reasoning. The model scores 91.7 on GPQA Diamond, 35.9 on HLE, 90.6 on MathVision without CI and 95.7 with CI, and 84.6 on CharXiv without CI and 90.6 with CI. It can support chart interpretation, visual math, scientific question answering, and multidisciplinary analysis. The HLE result remains below Claude-Opus-4.6 (Max) at 40.0, so it should not be treated as the strongest option for every frontier reasoning task. Limitations The model is large despite its low 6B activated count. The 125B language-model weights, 51B n-gram embedding parameters, and 4B MTP parameters create substantial storage and memory demands. The provided material gives no VRAM requirement, quantization size, measured tokens-per-second result, latency figure, or recommended batch size. Do not infer hardware capacity from the activated-parameter count: n-gram embeddings and inactive weights still affect deployment memory, while framework implementation determines how much can be offloaded. The model has a native context length of 262,144 tokens, with extension up to 1,000,000 tokens. The repository does not state the quality or speed behavior at the extended limit. Long context also increases serving complexity, and the model card provides no end-to-end latency measurements. Qwen claims that Qwen Sparse Attention reduces long-context latency, but the supplied information does not quantify the reduction. Benchmark results show uneven strengths. Qwen3.8-Flash-Next leads the listed models on many agentic, coding, instruction-following, and multimodal rows, but it does not lead every task. On NL2Repo-Bench it scores 48.1, below DeepSeek-V4-Flash-0731 at 54.2. On HLE it scores 35.9, below Claude-Opus-4.6 (Max) at 40.0. On CharXiv without CI it scores 84.6, below Qwen3.7-Plus at 85.8, although its with-CI score is 90.6. Benchmark harnesses, prompts, temperatures, and judges differ, so these numbers do not establish universal quality rankings. The model operates in thinking mode by default and emits content in <think>\n...\n</think>\n\n before the final response. This can increase output length, cost, and latency. Non-thinking mode exists, but the supplied material does not include the actual disabling code. Sampling-parameter support varies by inference framework. The license is listed only as other. No license terms appear in the supplied README, so commercial use, redistribution, modification, and hosted-service obligations remain unresolved. The model card also does not provide a detailed bias, safety, privacy, or misuse analysis. Teams need their own evaluation and policy controls. How it compares Qwen3.8-Flash-Next-GGUF Pick Qwen3.8-Flash-Next when you need the original Transformers-format weights and direct compatibility with Transformers, vLLM, SGLang, or TokenSpeed. Pick the GGUF alternative when local deployment through GGUF-compatible tooling and quantization matter more than retaining the original weight format. The supplied information does not provide quantized file sizes, quality deltas, VRAM requirements, or speed measurements, so it cannot establish a numeric cost or accuracy advantage. Qwen3-Coder-Next Pick Qwen3.8-Flash-Next for a broader multimodal and agentic system: it includes a vision encoder, reaches 1M-token extensibility, and reports strong computer-use and visual-reasoning results. Pick Qwen3-Coder-Next for coding-agent and local-development workloads when its specialized design and 3B activated parameters are the priority. The key tradeoff is general multimodal breadth and higher reported agent scores versus a smaller, coding-focused deployment profile. Qwen3.6-35B-A3B Pick Qwen3.8-Flash-Next when its reported coding-agent, tool-use, long-context, and multimodal capabilities justify a larger deployment. Pick Qwen3.6-35B-A3B when a smaller 35B-total, 3B-activated model better fits local serving constraints. The supplied benchmark table does not include Qwen3.6-35B-A3B, so no direct quality, speed, or cost comparison is available. Qwen3.8-2.4T-A95B Pick Qwen3.8-Flash-Next when you need a much smaller open-weight model with 6B activated parameters and a practical path to self-hosting. Pick Qwen3.8-2.4T-A95B when maximum model capacity is more important than infrastructure cost and complexity. The supplied information gives no shared benchmark results, latency data, or pricing, so the tradeoff can be stated only as model scale versus deployment burden. Qwen3.5-35B-A3B Pick Qwen3.8-Flash-Next for the newer experimental architecture, 125B total parameters with 6B activated, 262K native context, and the listed multimodal agent results. Pick Qwen3.5-35B-A3B when its 35B-total, 3B-activated profile offers a better fit for constrained infrastructure. The supplied material does not include direct benchmark, speed, pricing, or VRAM comparisons. Technical specifications Qwen3.8-Flash-Next uses a causal language model with a vision encoder and includes both pre-training and post-training. Its architecture is an experimental preview for Qwen4. Total language-model parameters: 125B. Activated language-model parameters: 6B. N-gram embedding parameters: 51B. MTP parameters: 4B. Hidden dimension: 2,560. Token embedding size: 248,320, padded. N-gram embedding table: 20,000,000 entries, using bigrams and trigrams at layer 2. Layers: 48. Hidden layout: 12 repetitions of three Gated DeltaNet-to-MoE blocks followed by one Qwen Sparse Attention-to-MoE block. Gated DeltaNet: 48 linear-attention heads for V, 16 for QK, head dimension 128. Qwen Sparse Attention: 24 Q heads, 2 KV heads, head dimension 256, rotary position-embedding dimension 64. QSA indexer: MQA with 4 query heads and 1 shared key head; indexer head dimension 128. QSA budget: 512 blocks or 2,048 tokens. MoE: 512 experts; 10 routed experts plus 1 shared expert activated; expert intermediate dimension 640. Gated Residual: 4 branches; bottleneck rank 320. LM output size: 248,320, padded. MTP: one layer trained with multi-steps. Context: 262,144 tokens natively; extensible to 1,000,000 tokens. Model format: Hugging Face Transformers weights and configuration. Listed serving compatibility: Hugging Face Transformers, vLLM, SGLang, TokenSpeed, and other compatible systems. Recommended production serving engines: SGLang, KTransformers, or vLLM. Training recipe: Muon and AdamW applied to specific weight categories; batch-size warmups removed; training starts at the target batch size; refitted scaling laws support larger learning rates and fewer optimizer steps. Architecture innovations: QSA selects micro-blocks rather than individual tokens; Gated Residual uses an element-wise data-dependent read gate and per-branch scalar write gate; n-gram embeddings provide a parameter-scaling path designed for offloading and memory-constrained accelerators. Repository downloads shown in the supplied metadata: 2,551. Pipeline tag: image-text-to-text. Library metadata: transformers. Model tag: Text-to-Text. License metadata: other. The README provides no training-dataset name or size, training-step count, compute budget, VRAM requirement, quantization specification, measured inference speed, or pricing. Model inputs and outputs Inputs Text prompts for causal language-model generation. Multimodal inputs supported by the model type and image-text-to-text pipeline designation. Context up to 262,144 tokens natively. Context extension up to 1,000,000 tokens. Multi-turn conversations and agent trajectories. Tool-use workflows, when the surrounding serving or application framework supplies tools. Thinking-mode generation by default. Sampling parameters for thinking mode: temperature=1.0, top_p=0.95, top_k=20, min_p=0.0, presence_penalty=0.0, repetition_penalty=1.0. Sampling parameters for instruct or non-thinking mode: temperature=0.7, top_p=0.80, top_k=20, min_p=0.0, presence_penalty=1.5, repetition_penalty=1.0. Outputs Generated text from a causal language model. Thinking-mode output containing <think>...</think> before the final response. Final natural-language answers, code, plans, tool arguments, and agent actions as determined by the application. Vision-conditioned text responses for image-text-to-text workflows. The model card does not define a universal tool-call schema or built-in tool set for this open-weight release. Applications that expose thinking content should parse or filter the <think> section before presenting the final answer. Getting started The supplied README does not include a complete Python loading and inference example. It recommends API use for streamlined integration and lists deployment recipes for SGLang, vLLM, and TokenSpeed. For production or high-throughput workloads, use a dedicated serving engine and consult the framework-specific recipe. The official hosted service is Qwen Cloud; the hosted Qwen3.8-Flash version adds production features beyond this preview. Frequently asked questions Q: Can I use Qwen3.8-Flash-Next commercially? A: The metadata lists the license as other, but the supplied README does not state the license terms. Do not assume commercial permission; obtain and review the applicable license before deployment. Q: How much VRAM does Qwen3.8-Flash-Next require? A: No VRAM requirement is provided. The model has 125B language-model parameters, 51B n-gram embedding parameters, and 4B MTP parameters, so the 6B activated count does not describe total storage or memory needs. Q: What context length does it support? A: It supports 262,144 tokens natively and is extensible to 1,000,000 tokens. The README does not provide quality or latency measurements for the extended range. Q: Does it accept images? A: The model type includes a vision encoder, and the metadata uses the image-text-to-text pipeline tag. The supplied material does not specify image resolution, image file formats, preprocessing rules, or a complete multimodal code example. Q: Is thinking enabled by default? A: Yes. The model emits <think>...</think> content before the final response. The README provides separate sampling recommendations for thinking and instruct or non-thinking modes, but the supplied excerpt does not include the code for disabling thinking. Q: Which framework should I use for serving? A: The weights and configuration use Hugging Face Transformers format and are listed as compatible with Transformers, vLLM, SGLang, and TokenSpeed. For production or high-throughput serving, the README recommends SGLang, KTransformers, or vLLM. Q: How fast is inference? A: The supplied information gives no tokens-per-second or latency measurements. Qwen claims that QSA cuts long-context latency by selecting micro-blocks rather than individual tokens, but the README provides no numeric comparison. Q: Is this the same as the hosted Qwen3.8-Flash model? A: No. Qwen3.8-Flash is the official hosted version based on this architecture preview and adds production features, including 1M-token context by default and official built-in tools. Q: Can I fine-tune it? A: The repository provides post-trained Transformers weights and configuration, but the supplied material does not document a fine-tuning recipe, supported parameter-efficient method, or hardware plan. Transformers compatibility provides an integration path, not a confirmed fine-tuning procedure. Q: Where can I read the related research? A: The Qwen3 technical report is available through the Qwen3 technical report. The model README also identifies a Qwen3.8-Flash-Next technical report, but no internal link for that report is provided here. Click here to read the full guide to Qwen3.8-Flash-Next