Has Qwen3.8 Actually Launched? Only the Preview Is Available, While Open Weights Are Still Pending

Qwen3.8 is already available, but what is currently online is the Qwen3.8-Max-Preview model, with the model ID qwen3.8-max-preview. As of July 22, 2026, Qwen officials still label it as a preview model, and the official version and open-weight version have not yet been released.

This distinction is important: Qwen3.8 can now be experienced and called through the Qwen AI platform, but it cannot be assumed that the full model weights, technical reports, architectural details, and formal benchmarks have been made public.

Official documentation:

• Qwen AI Platform: Token Plan Personal Edition
• Qwen AI Platform: Thinking Mode
• Qwen AI Platform: OpenAI Chat API

Quick conclusion

If you just want to be the first to test programming, complex reasoning, multi-Agent or office tasks, you can start now; if the goal is local deployment, quantization, fine-tuning or long-term stable production, you still need to wait for the official weights and complete technical documentation.

What has Qwen3.8 actually released?

The currently confirmed product is Qwen3.8-Max-Preview. Qwen AI platform clearly states:

1. It is a preview version and capabilities will be continuously updated during the preview period.
2. After the preview is over, the current model may be offline or replaced by the official version.
3. Currently, access is mainly provided through Token Plan.
4. The model supports reasoning, text generation and visual understanding.
5. Official notice: The official version of Qwen3.8 will be released and the weight will be opened.

Therefore, “Qwen3.8 is online” and “Qwen3.8 is officially available with open weights” are two different things. The former has already happened, and the latter is still still pending.

What do 2.4T parameters mean?

The official preview of Qwen3.8 mentioned 2.4T parameters, which is about 2.4 trillion total parameters. But until the full technical report is released, the actual cost of inference cannot be judged based on this number alone.

For mixed expert models, at least you also need to know:

• How many parameters are activated for each Token;
• Number of experts and routing methods;
• Context window and attention structure;
• Video memory, bandwidth and communication requirements during inference;
• Whether to provide dense or MoE open-weight versions at different scales;
• What license is used for weighting.

The total parameters determine part of the upper limit of the model capacity, and the activation parameters and inference architecture more directly affect the speed and cost of each request. Before these data are made public, it is not appropriate to simply understand 2.4T as “the cost of inference must be several times that of the previous generation.”

What should you test with Qwen3.8-Max-Preview?

From the official platform positioning, Qwen3.8-Max-Preview is oriented towards complex reasoning and programming tasks. It is more suitable to prioritize testing the following scenarios:

Long process programming tasks

Don’t just test one algorithm question. You can give the model a small real repository and ask it to complete:

1. Read the project structure;
2. Locate a cross-file problem;
3. Give a modification plan;
4. Modify the code;
5. Execute tests;
6. Continue to repair based on errors;
7. Summarize changes and residual risks.

This kind of test can better observe the stability of the model in long contexts, tool calls and multi-step error correction.

Front-end implementation from a design

Prepare the same design screenshot and acceptance criteria to compare the results of Qwen3.8 with the currently used models:

• Whether the page structure is complete;
• Whether responsive layout is available;
• Whether the design has been changed without authorization;
• Whether a large number of duplicate components will be generated;
• Several rounds of corrections are required after the first generation;
• Will the final code pass the build with lint.

Just looking at whether the screenshot “looks good” can easily lead to subjective bias. It is best to record the build success rate, modification rounds and manual takeover time at the same time.

Data Analysis and Office Workflow

You can select an anonymized dataset and require the model to complete data cleaning, exception description, statistical summary and report generation. Focus on checking whether the numbers can be traced back to the original data, rather than just whether the reporting language flows smoothly.

Multi-Agent collaboration

If the platform or client supports multiple Agent, different roles can be responsible for analysis, execution, and review. The focus of the test is not the number of roles, but whether constraints are lost, repeated executions, or files overwrite each other when tasks are handed over.

How to call the API

Qwen3.8-Max-Preview Currently only Token Plan. After purchase or activation, you need to obtain the package-specific API Key and Base URL from the console. You cannot directly assume that it is the same as the ordinary pay-as-you-go address.

The following takes the OpenAI compatible interface as an example. Please replace the address with the Token Plan Base URL displayed on the console:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

curl "$QWEN_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $QWEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen3.8-max-preview",
    "messages": [
      {
        "role": "user",
        "content": "分析这个方案的风险，并给出可执行的验证步骤"
      }
    ],
    "stream": false
  }'

Python can use the OpenAI SDK:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

import os
from openai import OpenAI

client = OpenAI(
    api_key=os.environ["QWEN_API_KEY"],
    base_url=os.environ["QWEN_BASE_URL"],
)

response = client.chat.completions.create(
    model="qwen3.8-max-preview",
    messages=[
        {
            "role": "user",
            "content": "为这个 Python 项目设计一套分层测试方案。",
        }
    ],
    extra_body={
        "reasoning_effort": "high",
        "preserve_thinking": True,
    },
)

print(response.choices[0].message.content)

Using preserve_thinking in multi-turn conversations

The official API document has a special explanation for qwen3.8-max-preview: preserve_thinking defaults to true. During multiple rounds of dialogue, reasoning_content in the historical message needs to be returned completely.

If the client only saves ordinary content and ignores the inference field, the following may occur:

• The quality of subsequent answers declines;
• Multi-step tool tasks lose intermediate states;
• The request format does not meet the model expectations;
• The client seems to be compatible, but actually cannot continue the session stably.

Before accessing, you should confirm whether the SDK, proxy gateway, and chat client retain unknown fields. Do not splice reasoning_content directly into content. The official documentation clearly does not support this processing method.

How to choose reasoning_effort

Qwen3.8-Max-Preview supports three levels of inference strength: low, high and xhigh. The default is xhigh.

Not all requests require the highest reasoning level. If batch tasks use xhigh by default, a large amount of budget may be consumed on simple problems. A more prudent approach is to route models and reasoning levels according to task complexity.

Built-in tool support

The Qwen3.8-Max-Preview Harness tools listed on the Qwen AI platform include:

• Internet search;
• code interpreter;
• Web scraping;
• Search pictures by pictures;
• Wen search pictures.

These tools are provided by the platform and do not mean that the model weights are built into the browser or code execution environment. When migrating to other service providers or deploying locally in the future, you need to prepare the corresponding tools, permission control, and running sandbox again.

When it comes to code execution and web page access, there are also separate restrictions:

• File system readable and writable range;
• Network access whitelist;
• Single execution time;
• Number of child processes;
• Exposure of keys and environment variables;
• Download file size;
• High-risk Shell and Git commands.

Greater model capabilities do not automatically eliminate tool execution risk.

What we still cannot conclude

The most common problem in the preview stage is to write promotional information in advance to confirm the facts. The following should still await official information:

Open-weight license

The official stated that the weight will be opened, but the specific license, commercial scope, redistribution requirements and usage restrictions have not yet been fully announced.

Hardware requirements for local deployment

Even if the 2.4T total parameter model uses MoE, it does not mean that ordinary workstations can run it. Whether the smaller variants, quantized weights and inference framework support will be released simultaneously, you need to wait for the model card.

Published benchmark results

Internal task performance can be used to understand product positioning, but it cannot replace public data sets, third-party evaluations, and real business regression testing.

Stable model ID

Previews may be continually updated, calling the same model ID today as next week, and actual capabilities may have changed. Production estimates should save dates, request parameters, input samples, and complete outputs.

A reusable evaluation framework

Prepare 20 to 50 masked tasks from real business while having the current production model execute with Qwen3.8-Max-Preview. Record the following for each task:

Don’t just pick open questions that the model is good at, and don’t substitute a successful result for repeated testing. For the Agent model, completion rate and recoverability are usually more important than the perception of a single round of answers.

FAQ

Is Qwen3.8 officially available with open weights?

No. Currently available is qwen3.8-max-preview, and the official version and open weights have only been announced as coming soon.

Can it run in Ollama or llama.cpp?

There is currently no official Qwen3.8 open weight, and it cannot be directly downloaded and run like the smaller open-weight Qwen models. Third-party models of the same name cannot be considered official weights either.

Can a standard DashScope API key call the model directly?

The official documentation currently labels this model as only available for Token Plan. The exclusive API Key and Base URL provided by the Token Plan console should be used, and the actual permissions of the console shall prevail.

Is the preview suitable for production use?

Direct replacement is not recommended. Capabilities and interface behaviors may be adjusted during the preview period, and fixed sample regression, cost assessment, abnormal degradation, and data compliance checks should be performed first.

When will the official version be released?

Qwen has only announced information about upcoming releases and releasing open weights, without providing verifiable precise dates. If you encounter rumors of a specific release date, you should wait for confirmation from Qwen’s official model page, model card, or code repository.

Summary

The interest around Qwen3.8 is justified, but the accurate statement should be: Qwen3.8-Max-Preview has been launched, the official version has not yet been released, and the open weights are still pending.

The most worthwhile thing to do now is not to draw conclusions around parameter scale, but to use real tasks to verify its programming, reasoning, visual understanding and tool calling capabilities, while preserving complete test conditions. After the formal model cards, weights, licenses and public benchmarks are available, we can then judge whether local deployment and production migration are cost-effective.