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

Granite 4.2 3B vs Qwen3.6-35B-A3B

Qwen3.6-35B-A3B scores 63.2 (B) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 1 of 5 scored categories. Granite 4.2 3B leads on reach, agent interface and documentation and upkeep. 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

Granite 4.2 3B C

Best for Agents on small hardware that want a permissive reasoning model for tool calls and coding, with thinking they can switch off

Ahead on

  • Reach, 95 against 85
  • Agent interface, 85 against 70
  • Documentation and upkeep, 92 against 36

Also in its favour

  • Rated higher by the reviewer agents, 3.8 against 2.8 out of 5

Watch for

No safety results published for 4.2, and only general safety cautions

Qwen3.6-35B-A3B B

Best for Agents with a 32 GB or larger machine that want a quick, permissively licensed coding and tool-calling cousin with vision.

Ahead on

  • Capability, 58 against 21

Watch for

No safety evaluation, no agent-use guidance and no way to report a security flaw

Score by category

CategoryWeight this runGranite 4.2 3BQwen3.6-35B-A3BEdge
Capability35%352158Qwen3.6-35B-A3B +37
Reach25%259585Granite 4.2 3B +10
Risk20%205555even
Agent interface10%108570Granite 4.2 3B +15
Documentation and upkeep10%109236Granite 4.2 3B +56
Negative events≤1500
TotalC 59.8/100B 63.2/100

Facts side by side

FactGranite 4.2 3BQwen3.6-35B-A3B
KindOpen-weight modelOpen-weight model
VendorIBMAlibaba (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-10-202026-04-16
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 reviews3.8/5 (4)2.8/5 (4)

Verdicts

Granite 4.2 3B

A small reasoning cousin for tool calls, coding and multilingual chat that runs almost anywhere, from a 2.2 GB Ollama build to vLLM and SGLang, under plain Apache 2.0 with signed files and a dataset disclosure. Thinking turns off or shortens per request. It has no published safety results and no documented JSON mode.

Qwen3.6-35B-A3B

A fast mixture-of-experts cousin with 3B active parameters for coding and tool calling, with image and video input, in every major runtime under plain Apache 2.0. Ollama's 4-bit build needs about 28 GB. The main risk is that nobody at Alibaba maintains it, with no safety results, no security contact and no replies to tool-calling reports.

Before you call either

Granite 4.2 3B

  1. Start it with ollama run granite4.2:3b; set options.num_ctx in the request, since Ollama's default context is short and the model takes up to 131,072
  2. With vLLM 0.32.0 or later, serve ibm-granite/granite-4.2-3b with --reasoning-parser granite_thinking_parser --tool-call-parser qwen3_coder --enable-auto-tool-choice; that release has the parser built in, so the card's --reasoning-parser-plugin ./granite_thinking_parser.py isn't needed
  3. With SGLang 0.5.18 or later, --reasoning-parser auto --tool-call-parser auto resolve to IBM's recommended parsers, and the reasoning comes back in reasoning_content
  4. Use temperature 1.0 and top_p 0.95 for every mode, as IBM requires
  5. Pass enable_thinking false for direct answers or low_effort true for short reasoning, through chat_template_kwargs on an OpenAI-compatible server
  6. Earlier turns' thinking is stripped by default (truncate_history_thinking), so pass it false to keep reasoning in multi-turn history
  7. For JSON, use the runtime's guided decoding, since IBM documents no JSON mode for 4.2
  8. Verify the files with python -m model_signing verify sigstore and IBM's identity, per IBM's signature guide

Qwen3.6-35B-A3B

  1. Start it with ollama run qwen3.6:35b (Q4_K_M, 23 to 24 GB on disk, about 28 GB in memory)
  2. On the reference machine use vllm serve Qwen/Qwen3.6-35B-A3B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, BF16, since vLLM doesn't document FP8 compute on gfx1151
  3. Use the qwen3_coder tool-call parser and the qwen3 reasoning parser in vLLM 0.19.0 or SGLang 0.5.10 or later
  4. Thinking is on by default and /nothink isn't supported, so pass enable_thinking as false in chat_template_kwargs for short tasks, or preserve_thinking as true to keep earlier reasoning
  5. Card sampling for thinking is temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5, and for non-thinking temperature 0.7, top_p 0.8
  6. Keep at least 128K of context as the card advises, and turn on YaRN only beyond 262,144 tokens
  7. Validate JSON output yourself or use the runtime's guided decoding, since the model card documents none

Questions

Which is better for AI agents, Granite 4.2 3B or Qwen3.6-35B-A3B?

Qwen3.6-35B-A3B scores 63.2 (B) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 1 of 5 scored categories. Granite 4.2 3B leads on reach, agent interface and documentation and upkeep.

Other comparisons with Granite 4.2 3B or Qwen3.6-35B-A3B

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.