Qwen 3.6 Dense

Overview

Qwen3.6 Dense refers to Qwen3.6-27B, the first dense open-weight model in Alibaba’s Qwen3.6 family, released around 21–22 April 2026 by the Qwen team. It is a 27-billion-parameter causal language model with an integrated vision encoder: text, image, and video in one checkpoint, under a commercially friendly Apache 2.0 license. Official weights ship on Hugging Face (Qwen/Qwen3.6-27B) and ModelScope, with an optional FP8 build; you can also try it on Qwen Studio and call it via Alibaba Cloud Model Studio (qwen3.6-27b).

The headline claim is practical, not just leaderboard vanity: as a dense model it activates all ~27B parameters per token (no MoE routing), yet official agentic coding scores beat the previous open flagship Qwen3.5-397B-A17B (397B total / 17B active) on SWE-bench Verified, SWE-bench Pro, Terminal-Bench 2.0, and SkillsBench. The sibling open model is the sparse Qwen3.6-35B-A3B (≈3B active)—faster and cheaper to run, usually a step behind the dense 27B on hard agent work. Community shorthand on Reddit and Hacker News simply says “3.6 dense” or “27B” for this model.

Key features

• Dense 27B, production-shaped size — Hidden size 5120, 64 layers, ~248K vocab (padded), full dense activation. Easier to reason about than giant MoEs for single-GPU and small multi-GPU boxes.
• Hybrid Gated DeltaNet + Gated Attention — Layout pattern 16 × (3 × (Gated DeltaNet → FFN) → 1 × (Gated Attention → FFN)). Linear-attention DeltaNet layers cut long-context KV cost; full gated attention every fourth mixer keeps quality. Same hybrid lineage as Qwen3-Next / Qwen3.5.
• Native multimodal — Unified vision-language checkpoint: images and video with thinking and non-thinking modes. Strong OCR / document / spatial scores relative to peer open dense models (e.g. MMMU 82.9, OCRBench 89.4, AndroidWorld 70.3 on the official card).
• Long context — 262,144 tokens natively; extensible toward ~1,010,000 with YaRN-style extension. Official serving notes recommend keeping ≥128K when you care about multi-step thinking quality.
• Thinking + non-thinking modes — Default thinking wraps traces in <think>…</think>. Non-thinking (instruct) mode for lower latency. API extras: enable_thinking and preserve_thinking so multi-turn agent loops reuse prior reasoning instead of re-deriving it every turn.
• Agentic coding focus — Tuned for frontend workflows, repo-level edits, tool use, and terminal agents. Official numbers (Qwen scaffold / listed harnesses): SWE-bench Verified 77.2, SWE-bench Pro 53.5, Terminal-Bench 2.0 59.3 (ties Claude 4.5 Opus on that table), SkillsBench Avg5 48.2, LiveCodeBench v6 83.9, GPQA Diamond 87.8, AIME26 94.1.
• Multi-token prediction (MTP) — Speculative decoding heads land in SGLang, vLLM, LM Studio, and recent llama.cpp builds—community reports large token/s gains (e.g. ~20→33 t/s demos with one toggle).
• Apache 2.0 open weights — Download, fine-tune, and ship commercially without a restrictive research-only license. Hosted proprietary cousins (Plus / Max / 3.7-Max) stay on the API side.
• Day-one stack — Transformers, vLLM (≥0.19), SGLang (≥0.5.10), KTransformers, Unsloth GGUF/QAT-style quants, LM Studio, Ollama community builds, OpenClaw, Qwen Code, Claude Code via Anthropic-compatible DashScope base URL.

Pricing

The model files are free. You pay for hardware or for hosted tokens. Mid-2026 economics (check providers—rates move):

Path	What you pay	Notes
Self-host weights (HF / ModelScope / GGUF)	$0 model fee	Apache 2.0. Cost = GPU/CPU, power, ops. BF16 weights alone ~54 GB; Q4 GGUF ~16–18 GB class.
Qwen Studio	Free chat (product limits)	Fast evaluation of the dense model in browser.
Alibaba Cloud Model Studio (International)	~$0.60 in / ~$3.60 out per 1M tokens	Model id qwen3.6-27b; context band up to 256K listed. Free quota often ~1M tokens for 90 days after activation (region rules apply).
Model Studio (Chinese mainland)	~$0.41 in / ~$2.48 out per 1M	Lower list price; same model family; billing currency/region differ.
OpenRouter (multi-provider)	Often ~$0.29–$0.32 in / ~$2.40–$3.20 out	DeepInfra, Phala, Alibaba Cloud Int., others; 262K context listed. Shop latency and uptime.
SiliconFlow	~$0.30 in / ~$3.20 out	Dedicated 27B page; competitive with OpenRouter blended rates.
Sibling MoE host prices (context)	35B-A3B often ~$0.15–$0.38 in	Much cheaper tokens/sec when quality ceiling is lower.
Alibaba Coding Plan / Token Plans	From ~$50/mo coding; seats $30–$200	Bundled request/credit products—not pure per-token for the open weights alone.

Local VRAM / RAM floor (Unsloth approximate, weights only) — 27B: 3-bit ~15 GB, 4-bit ~18 GB, 6-bit ~24 GB, 8-bit ~30 GB, BF16 ~55 GB. KV cache for 128K–262K is extra—budget headroom or quantized KV (q8_0 cache tricks on llama.cpp) for long agent sessions. A 24 GB card (3090-class) commonly runs Q4_K_M with 64K–100K context; 32 GB (5090) users report solid agent loops at 5–6 bit with FP8 KV.

Limits & gotchas

• Not Claude Opus / Sonnet replacement for everything — Community consensus: excellent for local agentic coding, small-to-medium tasks, and “do the typing while I do the thinking.” Large greenfield features and long-horizon one-shots still favor frontier closed APIs for many teams.
• Dense is slower than the 35B MoE — Same series, different trade-off: 27B denser quality vs 35B-A3B ~3–4× tokens/s at lower active FLOPs. Hobbyist head-to-heads show MoE holding up on routine bugs; dense pulls ahead on subtle invariants and architectural judgment.
• Memory reality — Full BF16 serving is multi-GPU for comfortable context. Official SGLang/vLLM examples often use tp-size 8 for 262K. Consumer single-GPU work means GGUF/FP8 and context discipline.
• Stack versioning — Needs recent Transformers / vLLM ≥0.19 / SGLang ≥0.5.10. Older Ollama builds hit unknown architecture errors (qwen35). Prefer Unsloth or official cards over random quants for tool parsers.
• Harness quality dominates benchmarks — Official SWE / Terminal numbers use specific scaffolds, temps, and context. Your Claude Code / OpenCode / OpenClaw / Qwen Code setup will not magically match the blog table without similar tool wiring and preserve_thinking.
• Mac unified memory vs discrete GPU — M2 32 GB users report ~1 t/s at Q6; M-series Max/Ultra and RTX 4090/5090 class boxes are where “daily drive” claims come from (often 40–150 t/s depending on quant and MTP).
• Regional API and compliance — DashScope has Beijing / Singapore / US endpoints. Data residency, export, and enterprise DPA questions belong to Alibaba Cloud’s Model Studio security docs—not the open weights themselves. Self-host when data cannot leave your VPC.
• Multimodal on local runtimes — Vision needs matching mmproj / VL pipeline; some GGUF+Ollama paths still split text and vision awkwardly. API and full Transformers/vLLM paths are cleaner for image+agent work.

Community sentiment

r/LocalLLaMA and r/LocalLLM treated the April 2026 drop as a step-change: “first local model that actually holds up” for real coding sessions with Claude Code–style harnesses, not just chat demos. Recurring themes: dense 27B as the quality pick on a 24–48 GB card; 35B-A3B as the speed pick; Unsloth GGUFs as the default download path; aggressive 3-bit MLX quants still “holding together” better than expected because the dense training is robust.

Hacker News launch and follow-up threads (April–July 2026) echo the same split. Maintainers report daily use for C++ / library work on dual V100s or RTX 5090s; one production note claimed OpenCode tasks at 260K context and 40–60 t/s with little gap versus Sonnet 4.6 on their issue set—others push back that larger MoEs and closed frontier models still win hard agent marathons. Pricing on OpenRouter is used as a tongue-in-cheek quality signal (“if hosts charge more for 27B than bigger Gemma, believe the market”).

Use 27B dense when correctness and agent depth matter; use 35B-A3B when you are waiting on the spinner. Neither replaces your review process.

Who should use it

• Local-first engineers — Want a strong coding/agent model on one high-end workstation GPU without per-token bills for most of the day.
• Startups and product teams shipping agents — Need Apache 2.0 weights for VPC / on-prem, with an optional Model Studio or OpenRouter burst path.
• Teams standardizing on open harnesses — OpenClaw, Qwen Code, OpenCode, or Claude Code pointed at a DashScope Anthropic-compatible base URL.
• Multimodal document and UI workflows — Screenshots, OCR, frontend generation (QwenWebBench-style work) in the same model as text tools.
• Fine-tuners — Domain adapters on a 27B dense base that is still trainable with LoRA/QLoRA on accessible hardware (Unsloth Studio path).
• Not ideal if — You only have 8–12 GB VRAM and need max quality, you want zero harness work and maximum closed-model reliability, or you need the absolute cheapest tokens (prefer Flash/MoE or smaller models).

Alternatives

• Qwen — Broader Qwen family entry (hosted Plus/Max, earlier gens) when you want the full Alibaba stack, not only the 27B dense open weights.
• Gemma 4 — Google’s Apache 2.0 open family (to 31B dense / 26B MoE); strong local peer with a different safety and template profile.
• DeepSeek — Competitive open and API coding models; often stronger pure-reason pricing trade-offs depending on generation.
• Mistral — European open + API line; good when EU deployment and Mistral ecosystem matter more than Qwen’s agent harness fit.
• Claude / Claude Code — Closed frontier when long-horizon reliability and product polish beat self-host control.
• Ollama / LM Studio — Local runners rather than models; common ways to operate Qwen3.6-27B GGUFs day to day.
• Llama 3 — Meta open lineage if your stack and compliance path are already Llama-centric (capability band differs by version).

Verdict

Qwen3.6 Dense (Qwen3.6-27B) is one of the best “single-box open” coding and agent models of the mid-2026 local scene: Apache 2.0, real multimodal, hybrid long-context architecture, and agentic scores that embarrassed much larger prior MoEs on Qwen’s tables. Treat official benchmarks as harness-dependent, plan VRAM honestly, and pick dense 27B for quality versus 35B-A3B for speed. For many developers it became the default local daily driver—not because it erased Claude, but because it finally made self-hosted agentic coding feel like real work instead of a demo.