Qwen 3 Decoded

Qwen3 Instruct vs Thinking vs Coder: Model Selection Guide

GLM 5.2 is live! Opus-level intelligence at open-source rates. Pay per token on serverless. Try it today.

Blog

Qwen 3 Decoded Qwen3 Decoded: Choosing the Right Model For Your Task

PUBLISHED 8/1/2025

Table of Contents TL;DR: Your Qwen3 Model Selection Guide Qwen3 Architecture and Benchmark Differences for Each Model

Real-World Implementation Examples

Why Open Source Wins (Fireworks AI Perspective)

🔗 Resources

Table of Contents

“Which Qwen3 variant should I actually deploy?” With Thinking, Instruct, and Coder released simultaneously, confusion spiked. We stress-tested all three on your real workflows (same benchmarks as yesterday’s post) and found: • Qwen3 235B A22B Instruct beats o4 mini in reranking & classification (0.758 → 0.726 in live Fireworks traffic) • Qwen3 235B A22B Thinking 2507 dominates complex math (AIME25: 92.3 vs 81.5 – 11% jump) • Qwen3 Coder 480B A35B Instruct closes the gap with quality near GPT 4.1 (0.862 → 0.91 in live Fireworks traffic)

Your surgical guide to deploying the right variant →

TL;DR: Your Qwen3 Model Selection Guide

Forget generic "better performance" claims. Here's exactly when to use which model based on verified testing: Try models in Google Colab:

Open in Colab • Use Qwen3-Coder-480B-A35B-Instruct as a Full-Stack Web App Generator • Use Qwen3-235B-A22B-Thinking-2507 to solve advanced AIME math problems • Use Qwen3-235B-A22B-Instruct-2507 for Real-Time Customer Support Chat Response Generation

Qwen3 Architecture and Benchmark Differences for Each Model

Qwen3-Coder-480B-A35B-Instruct

A purpose-built evolution of the Qwen3 coding model series, engineered exclusively for agentic coding workflows, repository-scale development, and tool-driven software engineering. Unlike general-purpose predecessors, this variant achieves state-of-the-art performance in real-world coding tasks through specialized reinforcement learning and native long-context processing, delivering production-ready results comparable to Claude Sonnet in Agentic Coding, Browser-Use, and Tool-Use scenarios. Model Architecture & Core Differences

• Mixture-of-Experts (MoE) LLM • Parameters: 480B total (35B "active" per forward pass; 160 experts, 8 live simultaneously) • Layers: 62 • Heads: 96Q; 8 Key/Value (GQA-optimized for code efficiency) • Context Window: • Base models: Typically limited to 32K–128K tokens. • This release: Natively supports 262,144 tokens (256K), extendable to 1M tokens via Yarn extrapolation—enabling full-repository comprehension, dynamic PR analysis, and multi-step tool orchestration.

• Agentic Specialization: • Non-thinking mode only (zero thinking blocks; enable_thinking=False deprecated). • Optimized function-calling protocols for Qwen Code, CLINE, and IDE integrations. • Trained via long-horizon RL (20K parallel environments) for multi-turn tool interactions (e.g., SWE-Bench Verified).

• Instant code generation across 100+ programming languages—zero latency for IDEs, cli tools, and cost-efficient dev workflows.

This model eliminates speculative "reasoning" delays—outputs pure, executable code/function calls instantly. It's the first open-source model that rivals commercial APIs for software engineering. Our tests show it excels at real-world coding tasks with exceptional tool usage capabilities. Key Feature and Usability Updates

• Pure Execution Mode: The model operates exclusively in non-thinking mode—outputs only executable code/function calls with zero speculative reasoning blocks. You never see thinking artifacts or need enable_thinking=False; responses are instantly deployable to IDEs, CLI tools, and production pipelines. • Repository-Scale Context Handling: Natively processes 262K tokens (256K) with seamless Yarn extrapolation to 1M tokens, eliminating context fragmentation for full-repository analysis, PR reviews, and multi-file refactoring. No manual window management—just paste entire codebases. • Agentic Tool Mastery: Optimized for real-world tool orchestration (Qwen Code CLI, CLINE, browser automation) via RL-trained function-calling protocols. Achieves SWE-Bench Verified SOTA among open models through 20K parallel environment training, delivering Claude Sonnet 4-level tool fluency for browser-use, debugging, and API integrations.

Implementation tip:

• Supports only non-thinking mode and specifying enable_thinking=False is no longer required.

Here is an example using function calling in Fireworks using Qwen3-Coder-480B-A35B-Instruct: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101

from fireworks import LLM import json

llm = LLM ( model = "qwen3-coder-480b-a35b-instruct" , deployment_type = "serverless" , api_key = FIREWORKS_API_KEY )

Define the function tool for getting city population

tools = [ { "type" : "function" , "function" : {

The name of the function

"name" : "get_city_population" ,

A detailed description of what the function does

"description" : "Retrieve the current population data for a specified city." ,

Define the JSON schema for the function parameters

"parameters" : {

Always declare a top-level object for parameters

"type" : "object" ,

Properties define the arguments for the function

"properties" : { "city_name" : {

JSON Schema type

"type" : "string" ,

A detailed description of the property

"description" : "The name of the city for which population data is needed, e.g., 'San Francisco'." } , } ,

Specify which properties are required

"required" : [ "city_name" ] , } , } , } ]

Define a comprehensive system prompt

prompt = f""" You have access to the following function:

Function Name: ' { tools [ 0 ] [ "function" ] [ "name" ] } ' Purpose: ' { tools [ 0 ] [ "function" ] [ "description" ] } ' Parameters Schema: { json . dumps ( tools [ 0 ] [ "function" ] [ "parameters" ] , indent = 4 ) }

Instructions for Using Functions: 1. Use the function ' { tools [ 0 ] [ "function" ] [ "name" ] } ' to retrieve population data when required. 2. If a function call is necessary, reply ONLY in the following format: {{"city_name": "example_city"}} 3. Adhere strictly to the parameters schema. Ensure all required fields are provided. 4. Use the function...