This repo contains the full precision source code, in "safe tensors" format to generate GGUFs, GPTQ, EXL2, AWQ, HQQ and other formats.
The source code can also be used directly.
This model is for all use cases, but excels in CODING and programming in all major programming languages and many minor ones too.
This model is based on Qwen3-30B-A3B-Instruct-2507 (MOE, 128 experts, 8 activated), with Brainstorm 20X
(by DavidAU) - details at bottom of this page.
The Brainstorm adapter will improve general performance and "out of the box" thinking.
This creates a model of 42B parameters, 67 layers and 807 tensors.
This version has the NATIVE context of 256k.
This version (vs Brainstorm 40x, 53B version) can be used for both coding and creative use cases.
For coding, programming set expert to:
6-8 for general work.
10 for moderate work.
12-16 for complex work, long projects, complex coding.
And for longer context, and/or multi-turn -> increase experts by 1-2 to help with longer context/multi turn understanding.
Suggest min context 8k-16k for thinking/output.
Recommended settings - general:
Rep pen 1.05 to 1.1 ; however rep pen of 1 will work well (may need to raise it for lower quants/fewer activated experts)
Temp .3 to .6 (+- .2)
Topk of 20, 40 or 100
Topp of .95 / min p of .05
System prompt (optional) to focus the model better.
Suggest min context 8k-16k for thinking/output.
Creative Use Cases:
Rep pen of 1.05 or higher, especially if using a lower quant / lower temps.
Also use rep pen of 1.05 or higher with very short prompts.
You can set active experts as low as "4" for creative use cases.
Suggest min context 8k-16k for thinking/output.
This is the refined version -V1.4- from this project (see this repo for all settings, details, system prompts, example generations etc etc):
Over the past three months, we have continued to scale the thinking capability of Qwen3-30B-A3B, improving both the quality and depth of reasoning. We are pleased to introduce Qwen3-30B-A3B-Thinking-2507, featuring the following key enhancements:
Significantly improved performance on reasoning tasks, including logical reasoning, mathematics, science, coding, and academic benchmarks that typically require human expertise.
Markedly better general capabilities, such as instruction following, tool usage, text generation, and alignment with human preferences.
NOTE: This version has an increased thinking length. We strongly recommend its use in highly complex reasoning tasks.
image/jpeg
Model Overview
Qwen3-30B-A3B-Thinking-2507 has the following features:
Type: Causal Language Models
Training Stage: Pretraining & Post-training
Number of Parameters: 30.5B in total and 3.3B activated
Number of Paramaters (Non-Embedding): 29.9B
Number of Layers: 48
Number of Attention Heads (GQA): 32 for Q and 4 for KV
Number of Experts: 128
Number of Activated Experts: 8
Context Length: 262,144 natively.
NOTE: This model supports only thinking mode. Meanwhile, specifying enable_thinking=True is no longer required.
Additionally, to enforce model thinking, the default chat template automatically includes <think>. Therefore, it is normal for the model's output to contain only </think> without an explicit opening <think> tag.
For more details, including benchmark evaluation, hardware requirements, and inference performance, please refer to our blog, GitHub, and Documentation.
Performance
Gemini2.5-Flash-Thinking
Qwen3-235B-A22B Thinking
Qwen3-30B-A3B Thinking
Qwen3-30B-A3B-Thinking-2507
Knowledge
MMLU-Pro
81.9
82.8
78.5
80.9
MMLU-Redux
92.1
92.7
89.5
91.4
GPQA
82.8
71.1
65.8
73.4
SuperGPQA
57.8
60.7
51.8
56.8
Reasoning
AIME25
72.0
81.5
70.9
85.0
HMMT25
64.2
62.5
49.8
71.4
LiveBench 20241125
74.3
77.1
74.3
76.8
Coding
LiveCodeBench v6 (25.02-25.05)
61.2
55.7
57.4
66.0
CFEval
1995
2056
1940
2044
OJBench
23.5
25.6
20.7
25.1
Alignment
IFEval
89.8
83.4
86.5
88.9
Arena-Hard v2$
56.7
61.5
36.3
56.0
Creative Writing v3
85.0
84.6
79.1
84.4
WritingBench
83.9
80.3
77.0
85.0
Agent
BFCL-v3
68.6
70.8
69.1
72.4
TAU1-Retail
65.2
54.8
61.7
67.8
TAU1-Airline
54.0
26.0
32.0
48.0
TAU2-Retail
66.7
40.4
34.2
58.8
TAU2-Airline
52.0
30.0
36.0
58.0
TAU2-Telecom
31.6
21.9
22.8
26.3
Multilingualism
MultiIF
74.4
71.9
72.2
76.4
MMLU-ProX
80.2
80.0
73.1
76.4
INCLUDE
83.9
78.7
71.9
74.4
PolyMATH
49.8
54.7
46.1
52.6
$ For reproducibility, we report the win rates evaluated by GPT-4.1.
& For highly challenging tasks (including PolyMATH and all reasoning and coding tasks), we use an output length of 81,920 tokens. For all other tasks, we set the output length to 32,768.
Quickstart
The code of Qwen3-MoE has been in the latest Hugging Face transformers and we advise you to use the latest version of transformers.
With transformers<4.51.0, you will encounter the following error:
KeyError: 'qwen3_moe'
The following contains a code snippet illustrating how to use the model generate content based on given inputs.
python
1from transformers import AutoModelForCausalLM, AutoTokenizer
23model_name ="Qwen/Qwen3-30B-A3B-Thinking-2507"45# load the tokenizer and the model6tokenizer = AutoTokenizer.from_pretrained(model_name)7model = AutoModelForCausalLM.from_pretrained(8 model_name,9 torch_dtype="auto",10 device_map="auto"11)1213# prepare the model input14prompt ="Give me a short introduction to large language model."15messages =[16{"role":"user","content": prompt}17]18text = tokenizer.apply_chat_template(19 messages,20 tokenize=False,21 add_generation_prompt=True,22)23model_inputs = tokenizer([text], return_tensors="pt").to(model.device)2425# conduct text completion26generated_ids = model.generate(27**model_inputs,28 max_new_tokens=3276829)30output_ids = generated_ids[0][len(model_inputs.input_ids[0]):].tolist()3132# parsing thinking content33try:34# rindex finding 151668 (</think>)35 index =len(output_ids)- output_ids[::-1].index(151668)36except ValueError:37 index =03839thinking_content = tokenizer.decode(output_ids[:index], skip_special_tokens=True).strip("\n")40content = tokenizer.decode(output_ids[index:], skip_special_tokens=True).strip("\n")4142print("thinking content:", thinking_content)# no opening <think> tag43print("content:", content)44
For deployment, you can use sglang>=0.4.6.post1 or vllm>=0.8.5 or to create an OpenAI-compatible API endpoint:
Note: If you encounter out-of-memory (OOM) issues, you may consider reducing the context length to a smaller value. However, since the model may require longer token sequences for reasoning, we strongly recommend using a context length greater than 131,072 when possible.
For local use, applications such as Ollama, LMStudio, MLX-LM, llama.cpp, and KTransformers have also supported Qwen3.
Agentic Use
Qwen3 excels in tool calling capabilities. We recommend using Qwen-Agent to make the best use of agentic ability of Qwen3. Qwen-Agent encapsulates tool-calling templates and tool-calling parsers internally, greatly reducing coding complexity.
To define the available tools, you can use the MCP configuration file, use the integrated tool of Qwen-Agent, or integrate other tools by yourself.
python
1from qwen_agent.agents import Assistant
23# Define LLM4# Using Alibaba Cloud Model Studio5llm_cfg ={6'model':'qwen3-30b-a3b-thinking-2507',7'model_type':'qwen_dashscope',8}910# Using OpenAI-compatible API endpoint. It is recommended to disable the reasoning and the tool call parsing11# functionality of the deployment frameworks and let Qwen-Agent automate the related operations. For example, 12# `VLLM_USE_MODELSCOPE=true vllm serve Qwen/Qwen3-30B-A3B-Thinking-2507 --served-model-name Qwen3-30B-A3B-Thinking-2507 --tensor-parallel-size 8 --max-model-len 262144`.13#14# llm_cfg = {15# 'model': 'Qwen3-30B-A3B-Thinking-2507',16# 17# # Use a custom endpoint compatible with OpenAI API:18# 'model_server': 'http://localhost:8000/v1', # api_base without reasoning and tool call parsing19# 'api_key': 'EMPTY',20# 'generate_cfg': {21# 'thought_in_content': True,22# },23# }242526# Define Tools27tools =[28{'mcpServers':{# You can specify the MCP configuration file29'time':{30'command':'uvx',31'args':['mcp-server-time','--local-timezone=Asia/Shanghai']32},33"fetch":{34"command":"uvx",35"args":["mcp-server-fetch"]36}37}38},39'code_interpreter',# Built-in tools40]4142# Define Agent43bot = Assistant(llm=llm_cfg, function_list=tools)4445# Streaming generation46messages =[{'role':'user','content':'https://qwenlm.github.io/blog/ Introduce the latest developments of Qwen'}]47for responses in bot.run(messages=messages):48pass49print(responses)
Best Practices
To achieve optimal performance, we recommend the following settings:
Sampling Parameters:
We suggest using Temperature=0.6, TopP=0.95, TopK=20, and MinP=0.
For supported frameworks, you can adjust the presence_penalty parameter between 0 and 2 to reduce endless repetitions. However, using a higher value may occasionally result in language mixing and a slight decrease in model performance.
Adequate Output Length: We recommend using an output length of 32,768 tokens for most queries. For benchmarking on highly complex problems, such as those found in math and programming competitions, we suggest setting the max output length to 81,920 tokens. This provides the model with sufficient space to generate detailed and comprehensive responses, thereby enhancing its overall performance.
Standardize Output Format: We recommend using prompts to standardize model outputs when benchmarking.
Math Problems: Include "Please reason step by step, and put your final answer within \boxed{}." in the prompt.
Multiple-Choice Questions: Add the following JSON structure to the prompt to standardize responses: "Please show your choice in the answer field with only the choice letter, e.g., "answer": "C"."
No Thinking Content in History: In multi-turn conversations, the historical model output should only include the final output part and does not need to include the thinking content. It is implemented in the provided chat template in Jinja2. However, for frameworks that do not directly use the Jinja2 chat template, it is up to the developers to ensure that the best practice is followed.
For all settings used for this model (including specifics for its "class"), including example generation(s) and for advanced settings guide (which many times addresses any model issue(s)), including methods to improve model performance for all use case(s) as well as chat, roleplay and other use case(s) please see:
However I went in a completely different direction from what was outlined in this paper.
What is "Brainstorm" ?
The reasoning center of an LLM is taken apart, reassembled, and expanded.
In this case for this model: 20 times
Then these centers are individually calibrated. These "centers" also interact with each other.
This introduces subtle changes into the reasoning process.
The calibrations further adjust - dial up or down - these "changes" further.
The number of centers (5x,10x etc) allow more "tuning points" to further customize how the model reasons so to speak.
The core aim of this process is to increase the model's detail, concept and connection to the "world",
general concept connections, prose quality and prose length without affecting instruction following.
This will also enhance any creative use case(s) of any kind, including "brainstorming", creative art form(s) and like case uses.
Here are some of the enhancements this process brings to the model's performance:
Prose generation seems more focused on the moment to moment.
Sometimes there will be "preamble" and/or foreshadowing present.
Fewer or no "cliches"
Better overall prose and/or more complex / nuanced prose.
A greater sense of nuance on all levels.
Coherence is stronger.
Description is more detailed, and connected closer to the content.
Simile and Metaphors are stronger and better connected to the prose, story, and character.
Sense of "there" / in the moment is enhanced.
Details are more vivid, and there are more of them.
Prose generation length can be long to extreme.
Emotional engagement is stronger.
The model will take FEWER liberties vs a normal model: It will follow directives more closely but will "guess" less.
The MORE instructions and/or details you provide the more strongly the model will respond.
Depending on the model "voice" may be more "human" vs original model's "voice".
Other "lab" observations:
This process does not, in my opinion, make the model 5x or 10x "smarter" - if only that was true!
However, a change in "IQ" was not an issue / a priority, and was not tested or calibrated for so to speak.
From lab testing it seems to ponder, and consider more carefully roughly speaking.
You could say this process sharpens the model's focus on it's task(s) at a deeper level.
The process to modify the model occurs at the root level - source files level. The model can quanted as a GGUF, EXL2, AWQ etc etc.