Qwen 3.6 27B: Dense Coding Model Beating a 397B MoE, 262K Context

TL;DR

Last updated July 2026.

Qwen 3.6 27B is an open-weight (Apache 2.0) dense coding model from Alibaba's Qwen team, released April 2026. It has 27B total parameters, all active on every token, a 262,144-token native context extensible to about 1M via YaRN, and multimodal input (text, image, video). On SWE-bench Verified it scores 77.2, ahead of the 397B Qwen 3.5 mixture-of-experts (76.2) it succeeds, and 53.5 on SWE-bench Pro. It fits on a single 24GB GPU at 4-bit and a single 40GB GPU in FP8.

What Is Qwen 3.6 27B?

Qwen 3.6 27B is an open-weight dense coding model from Alibaba's Qwen team, released April 2026 under the Apache 2.0 license. It has 27B total parameters, all active on every forward pass (a dense model, not a mixture-of-experts), a 262,144-token native context extensible to about 1,010,000 tokens via YaRN, and a recommended 81,920-token max output. It accepts text, image, and video input through a unified processor and supports 201 languages. The weights shipped on Hugging Face (Qwen/Qwen3.6-27B) day-one, with FP8, GPTQ-Int4, NVFP4, and GGUF quants following.

It is a coding-first model. On SWE-bench Verified it posts 77.2, ahead of the 397B-parameter Qwen 3.5 MoE it replaces, while activating one-fourteenth the total parameters. It runs on vLLM, SGLang, and llama.cpp, and drops into Claude Code or Cline with a config change. Morph serves it as morph-qwen36-27b on custom kernels via an OpenAI-compatible API, positioned as the dense, low-latency option in the lineup. See Morph Open Source Models and pricing.

Architecture: The Gated DeltaNet Hybrid

Qwen 3.6 27B's defining choice is a hybrid attention stack. Its 64 layers are arranged as 16 identical blocks; each block is three (Gated DeltaNet then FFN) sublayers followed by one (Gated Attention then FFN) layer. So three of every four attention sublayers use Gated DeltaNet, a linear-attention variant with linear cost in sequence length, and only one uses full Gated Attention. That linear-attention majority is what makes the 262K context economical to serve on a single card: most of the sequence-length work never pays the quadratic attention tax.

Thinking Preservation

Qwen calls out one agentic feature: Thinking Preservation, which retains reasoning traces across multi-turn conversations rather than regenerating them each turn. In a long agent loop that cuts redundant reasoning-token generation. Treat the exact mechanism as first-party-described; independent measurement of the token savings was limited at launch.

Benchmarks vs the 397B MoE and the Frontier

The headline is that a 27B dense model beats the 397B MoE it replaces on every reported coding benchmark. On SWE-bench Verified Qwen 3.6 27B scores 77.2 versus 76.2; on SWE-bench Pro 53.5 versus 50.9; on Terminal-Bench 2.0 59.3 versus 52.5. Qwen reports these using its own agent scaffold, and independent third-party reproductions outside that scaffold were limited as of April 2026, so read them as first-party.

Against the closed frontier, the coding score is competitive but not leading. Qwen 3.6 27B's 77.2 SWE-bench Verified sits below Claude Opus 4.6 (80.8) and Opus 4.7 (84.3), and Qwen benchmarked against Claude 4.5 Opus rather than the current 4.8 release, so the "matches Opus on Terminal-Bench" framing compares to an older Claude. GPQA-Diamond (87.8) is externally verifiable and holds up. See our SWE-bench Pro breakdown for how these harnesses behave and where scaffolds inflate scores.

Why a 27B Dense Model Beats a 397B MoE

The interesting result is not the score, it is the shape. A 27B dense model matching a 397B mixture-of-experts on coding means flagship-tier agentic work now fits on one GPU. But the 397B-vs-27B gap is misleading: the older model is a mixture-of-experts that activates only 17B parameters per token, so on active-parameter terms the two are closer (27B dense vs 17B active). Qwen 3.6 wins by being fully dense (every parameter contributes to every token) and by the newer training recipe, not by being 14x smaller in the way that flatters.

Dense has two consequences. First, latency: no expert routing, no all-to-all communication, so time-to-first-token and per-token latency are low, which is why Morph positions morph-qwen36-27b as the dense, low-latency model in the lineup. Second, throughput: a dense 27B does 27B FLOPs of work per token, versus 17B for the A17B MoE, so tokens-per-second per GPU is lower than a sparsely-activated model of similar quality. You trade aggregate throughput for simplicity, low latency, and single-card fit.

Serving Footguns: Ollama, vLLM, and llama.cpp

The most-upvoted r/LocalLLaMA diagnosis of "Qwen 3.6 is unreliable" is a runtime problem, not a model problem: users report that switching from Ollama to llama.cpp with current unsloth quants eliminates context drift, tool-use failures, and performance issues. Ollama also struggles with the separate mmproj vision file. The Gated DeltaNet hybrid needs recent operator support, so run a current llama.cpp or vLLM build, not whatever ships by default.

# vLLM >= 0.17.0, single 40GB GPU (FP8)
vllm serve Qwen/Qwen3.6-27B-FP8 \
  --max-model-len 262144 \
  --reasoning-parser qwen3 \
  --enable-auto-tool-choice \
  --tool-call-parser qwen3_coder

# Text-only (skip the vision encoder):
#   --language-model-only
# ~1M context via YaRN:
#   --hf-overrides '{"rope_scaling":{"rope_type":"yarn","factor":4.0}}'

Four more footguns from the vLLM recipe and community reports:

• Tool-call JSON errors run ~12%. One third-party review measured about 12% malformed-JSON tool calls versus 0.5% for Claude. That makes unsupervised autonomous runs unreliable: gate tool invocations, or use the model as the reasoning layer and let a stricter model execute.
• The default 4-bit quant drifts. The ~17GB Q4 quant drifts on extended agentic runs, and reports of drift past ~14K tokens correlate with 4-bit weights plus low-precision KV cache. The practical floor for agentic work is Q8-class weights (~30GB) with F16/BF16 KV cache, which holds to 100K-160K.
• CUDA 13.2 can output gibberish. A known incompatibility on some stacks produces garbage output. Pin a known-good CUDA/runtime combination rather than assuming a bad model.
• Disable thinking explicitly. To turn off reasoning, pass --default-chat-template-kwargs '{"enable_thinking": false}'. For CUDA-graph errors, lower --max-cudagraph-capture-size below the default 512; Mamba/DeltaNet prefix caching is still experimental.

Self-host memory reality

Qwen 3.6 27B is the rare flagship-tier coding model that fits on one consumer card. The vLLM recipe lists Int4 on a single 24GB GPU (RTX 4090), FP8 on a single 40GB GPU (H100/H200/L40S), and BF16 on one H200 or two H100s. A 24GB unified-memory Mac runs the 4-bit build well; a 48GB Mac is described as "just barely" enough for Q8 plus context and dev tools. On Apple Silicon, the dedicated MLX coding checkpoints avoid the drift the generic 4-bit GGUF shows.

Pricing and How to Run It on Morph

The weights are free under Apache 2.0, so "pricing" means hosted API access. OpenRouter routes it at about $0.28/M input and $2.38/M output, Alibaba Cloud DashScope sells it per token, and Qwen Studio offers a free tier. Morph serves morph-qwen36-27b at $0.289/M input and $2.40/M output with a 131,072-token context, on custom kernels via an OpenAI-compatible API.

Serving fidelity is where hosts diverge. Many serverless providers quantize activations to FP8 or lower to cut cost, and Qwen 3.6's default 4-bit quant is exactly the one that drifts on long runs. Morph Open Source Models serves Qwen 3.6 27B with codegen-tuned kernels built for code generation. Run it against the same OpenAI-compatible endpoint as every other Morph model:

from openai import OpenAI

client = OpenAI(
    base_url="https://api.morphllm.com/v1",
    api_key="YOUR_MORPH_API_KEY",
)

resp = client.chat.completions.create(
    model="morph-qwen36-27b",
    messages=[
        {"role": "user", "content": "Refactor this function to remove the nested loop."},
    ],
)
print(resp.choices[0].message.content)

Qwen 3.6 API: Pricing and How to Call It

Qwen 3.6 27B is available through an OpenAI-compatible API. On Morph it is served as morph-qwen36-27b at $0.289/M input and $2.40/M output with a 131,072-token context, hit at https://api.morphllm.com/v1 with a Bearer token. Alibaba Cloud (DashScope) runs the first-party API, and OpenRouter routes to third-party hosts. Every host exposes the same open weights; the difference is per-token price and how the host serves activations (reference weights vs quantized).

from openai import OpenAI

client = OpenAI(
    base_url="https://api.morphllm.com/v1",
    api_key="YOUR_MORPH_API_KEY",  # Authorization: Bearer <key>
)

resp = client.chat.completions.create(
    model="morph-qwen36-27b",
    messages=[
        {"role": "user", "content": "Explain this stack trace and propose a fix."},
    ],
)
print(resp.choices[0].message.content)

Sources: Morph rates from morphllm.com/pricing; OpenRouter routed price from openrouter.ai/qwen/qwen3.6-27b (listed April 27, 2026); DashScope from Alibaba Cloud's Qwen pricing. Marketplace routers vary by upstream host and quantization, so a cheaper sticker can mean FP8-quantized activations rather than reference weights.

Getting a Qwen 3.6 API key

For the Morph endpoint, sign up at morphllm.com, create a key in the dashboard, and pass it as Authorization: Bearer YOUR_MORPH_API_KEY against https://api.morphllm.com/v1; the same key works for every model in the Open Source Models lineup, including Qwen 3.5, MiniMax M3, and DeepSeek V4 Flash. For the first-party API, create a key in Alibaba Cloud's DashScope console and use its base URL instead.

Use Qwen 3.6 27B in Claude Code and Cline

Claude Code

Qwen 3.6 27B has no first-party Anthropic-format endpoint, so the clean path is an OpenAI-compatible base URL. Point Claude Code at Morph:

export ANTHROPIC_BASE_URL="https://api.morphllm.com/v1"
export ANTHROPIC_AUTH_TOKEN="your-morph-key"
export ANTHROPIC_DEFAULT_SONNET_MODEL="morph-qwen36-27b"
claude

To self-host, serve with vLLM (--reasoning-parser qwen3, --enable-auto-tool-choice --tool-call-parser qwen3_coder) and front it with an Anthropic-to-OpenAI shim, or use llama.cpp with a Q8-class quant. For routing Qwen 3.6 alongside other providers behind one endpoint, see Claude Code with LiteLLM.

Cline

Cline uses an OpenAI-compatible provider. Set the base URL to https://api.morphllm.com/v1, the model to morph-qwen36-27b, and the context window to 131072. To self-host, point Cline at your vLLM/llama.cpp endpoint and model Qwen/Qwen3.6-27B. Because tool-call JSON errors run higher than a frontier model, review the first few agent runs before trusting unsupervised edits.

Qwen 3.6 27B vs the MoE Sibling, GLM, and DeepSeek

Among open-weight coding models, Qwen 3.6 27B is the density play: the strongest single-GPU coding model, but not the top absolute score. The larger Qwen 3.6-35B-A3B MoE trades single-card fit for higher throughput; GLM-5.2 leads SWE-bench Pro at a far larger size; DeepSeek V4 is cheaper per token at the API.

SWE-bench figures here mix Verified and Pro across trackers and scaffolds, so read cross-model rows as directional, not head-to-head; harness and verifier differences move these by several points. See GLM-5.2 and DeepSeek V4 for those models' full breakdowns, and Qwen 3.5 for the 397B predecessor.

Qwen 3.6 27B: Pros and Cons

When to Use Qwen 3.6 27B (and When Not)

Frequently Asked Questions

What is Qwen 3.6 27B?

An open-weight (Apache 2.0) dense coding model from Alibaba's Qwen team, released April 2026. 27B total parameters, all active (not MoE), 262K native context (~1M via YaRN), multimodal input. It scores 77.2 on SWE-bench Verified, ahead of the 397B Qwen 3.5 MoE it replaces. Weights on Hugging Face (Qwen/Qwen3.6-27B).

How does a 27B model beat a 397B model?

The 397B Qwen 3.5 is a mixture-of-experts that activates only 17B parameters per token, so on active-parameter terms it is 27B dense vs 17B active. Qwen 3.6 wins by being fully dense and by the newer training recipe: 77.2 vs 76.2 on SWE-bench Verified, 53.5 vs 50.9 on Pro, 59.3 vs 52.5 on Terminal-Bench 2.0 (first-party).

How much does Qwen 3.6 27B cost?

The weights are free (Apache 2.0). For hosted APIs, OpenRouter routes it at about $0.28/M input and $2.38/M output, and Morph serves morph-qwen36-27b at $0.289/M input and $2.40/M output. Cheaper routed stickers can mean FP8-quantized activations rather than reference weights.

What is Qwen 3.6 27B's context window?

262,144 tokens native, extensible to about 1,010,000 via YaRN. Community reports note drift past ~14K tokens on 4-bit quants with low-precision KV cache; Q8-class weights with F16/BF16 KV cache hold to 100K-160K, so "fits in memory" and "usable at long context" are different things.

Why is Qwen 3.6 27B tool calling unreliable?

Two causes: runtime (Ollama is the most-reported source of failures; llama.cpp with current unsloth quants fixes most of it) and the model (about 12% malformed-JSON tool calls in one third-party test vs 0.5% for Claude). On vLLM, enable --enable-auto-tool-choice --tool-call-parser qwen3_coder.

Can I self-host Qwen 3.6 27B?

Yes, under Apache 2.0. Int4 fits a single 24GB GPU (RTX 4090), FP8 a single 40GB GPU (H100/H200/L40S), BF16 one H200 or two H100s. The default 4-bit quant drifts on long runs; Q8-class weights (~30GB) are the practical floor for agentic work.

Is Qwen 3.6 27B multimodal?

Yes. It accepts text, image, and video input through a unified processor and posts 82.9 on MMMU and 87.7 on VideoMME. For text-only serving on vLLM, skip the vision encoder with --language-model-only. Ollama has trouble with the separate mmproj vision file, which is one more reason to prefer llama.cpp.