Head to head · Open-weight models you run yourself · October 2026 research run

Darwin-36B-Opus vs Qwen3-Coder-30B-A3B-Instruct

Darwin-36B-Opus scores 61 (C) on agent readiness against Qwen3-Coder-30B-A3B-Instruct's 55.7 (C), and leads in 1 of 4 scored categories. Qwen3-Coder-30B-A3B-Instruct leads on reach and agent interface. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

Darwin-36B-Opus C

Best for Reasoning-heavy text tasks on a 32 GB machine or a single 80 GB GPU, where a disclosed training method isn't required

Ahead on

  • Documentation and upkeep, 51 against 31

Watch for

The merge method is proprietary and the current weights include an undescribed targeted refinement

Qwen3-Coder-30B-A3B-Instruct C

Best for Coding agents and local coding tools that want a fast, capable open model on one 24 GB GPU or a 32 GB Mac, with a plain licence.

Ahead on

  • Reach, 90 against 80
  • Agent interface, 75 against 70

Watch for

No safety results, prompt-injection guidance or security contact, though it's meant to run commands

Score by category

CategoryWeight this runDarwin-36B-OpusQwen3-Coder-30B-A3B-InstructEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258090Qwen3-Coder-30B-A3B-Instruct +10
Risk20%205555even
Agent interface10%107075Qwen3-Coder-30B-A3B-Instruct +5
Documentation and upkeep10%105131Darwin-36B-Opus +20
Negative events≤1500
TotalC 61/100C 55.7/100

Facts side by side

FactDarwin-36B-OpusQwen3-Coder-30B-A3B-Instruct
KindOpen-weight modelOpen-weight model
VendorFINAL-Bench (VIDRAFT)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-04-232025-12-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.5/5 (4)2.8/5 (4)

Verdicts

Darwin-36B-Opus

A text-only reasoning cousin merged from Qwen3.6-35B-A3B and a reasoning-distilled fine-tune of it, with about 3B active parameters. It needs 32 GB for the publisher's 4-bit GGUF or about 83 GB in BF16, and runs in vLLM, SGLang, Transformers and llama.cpp. The main risks are an undisclosed merge method, a card that disagrees with its files, and no safety results.

Qwen3-Coder-30B-A3B-Instruct

A fast coding cousin, with 3.3B of 30.5B parameters active per token, for agentic coding tools, repository reading and fill-in-the-middle without a thinking step. It needs about 21 to 23 GB at 4 bits, and several providers host it. The main risk is that it runs commands for agents with no safety results or guidance, and Alibaba doesn't answer users.

Before you call either

Darwin-36B-Opus

  1. Quickest start is llama-server -hf FINAL-Bench/POCKET-35B-GGUF:Q4_K_M --jinja, about 21 GB of files
  2. On the reference machine BF16 fits, vllm serve FINAL-Bench/Darwin-36B-Opus --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parsers for Qwen3.6's format
  3. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  4. The card suggests temperature 0.6 to 0.7 and at least 5,120 new tokens for its think traces
  5. generation_config.json stops only on the end-of-text token, so add <|im_end|> as a stop token if a runtime keeps generating after the turn ends
  6. Text only, the vision encoder of Qwen3.6-35B-A3B isn't in these files
  7. Validate JSON output yourself, since structured output isn't documented

Qwen3-Coder-30B-A3B-Instruct

  1. Quickest start is ollama run qwen3-coder:30b, 19 GB
  2. On our reference machine use BF16 with vllm serve Qwen/Qwen3-Coder-30B-A3B-Instruct --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder, 61 GB of weights fits the GPU share
  3. Use the qwen3_coder parser in vLLM or SGLang, not hermes, since calls come back as function and parameter blocks rather than JSON
  4. Pass tool-call arguments in the history as objects, the template iterates them as a mapping
  5. Sampling per the card is temperature 0.7, top_p 0.8, top_k 20 and repetition_penalty 1.05, with up to 65,536 output tokens
  6. For code completion use the fill-in-the-middle tokens <|fim_prefix|>, <|fim_suffix|> and <|fim_middle|> from Qwen's README
  7. Sandbox the commands and files it touches, since nothing from Alibaba covers prompt injection

Questions

Which is better for AI agents, Darwin-36B-Opus or Qwen3-Coder-30B-A3B-Instruct?

Darwin-36B-Opus scores 61 (C) on agent readiness against Qwen3-Coder-30B-A3B-Instruct's 55.7 (C), and leads in 1 of 4 scored categories. Qwen3-Coder-30B-A3B-Instruct leads on reach and agent interface.

Other comparisons with Darwin-36B-Opus or Qwen3-Coder-30B-A3B-Instruct

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.