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

Inkling 2 Mini vs Qwen3-Coder-30B-A3B-Instruct

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

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

Which one, for what

Inkling 2 Mini C

Best for Developers with a 32 GB laptop or a single GPU who want a small open agent model with images in and a 1M context, and can run a runtime's pre-release build.

Ahead on

  • Risk, 70 against 55
  • Agent interface, 85 against 75
  • Documentation and upkeep, 57 against 31

Watch for

No released version of vLLM, SGLang, Transformers, llama.cpp or Ollama runs it on 20 November 2026

Qwen3-Coder-30B-A3B-Instruct C

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

Ahead on

  • Reach, 90 against 60

Watch for

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reach Qwen3-Coder-30B-A3B-Instruct +30

Inkling 2 Mini 60

Memory 25 of 30, ggml-org's IQ4_NL GGUF with its vision projector is 17.98 GB, about 21.6 GB with a fifth added. Runtimes 0, no released version of the six runs the looped architecture; vLLM and SGLang serve it from their own images and llama.cpp has it on master only. Builds 10, one checkpoint from the publisher in mixed NVFP4 and MXFP8. Terms 10, Apache 2.0 with a binding acceptable use policy on top, read as a custom licence. Download 10, no gate. Hosted 5, Thinking Machines' own Tinker samples from it. 25 + 0 + 10 + 10 + 10 + 5 = 60.

Qwen3-Coder-30B-A3B-Instruct 90

Memory 25 of 30, LM Studio's MLX 4-bit build is 17.2 GB and Ollama's 4-bit build 19 GB, 21 to 23 GB with a fifth added, which fits 24 GB. Runtimes 25, released Transformers, vLLM, SGLang and llama.cpp run the qwen3_moe architecture, vLLM and SGLang carry a qwen3_coder parser, Ollama's released build pins a llama.cpp that has qwen3moe, and LM Studio's catalogue carries it. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, Featherless AI on Hugging Face (live on 4 November 2026) plus SiliconFlow and Amazon Bedrock on OpenRouter (per 21 October, not re-read) serve it. 25 + 25 + 10 + 15 + 10 + 5 = 90.

Documentation and upkeep Inkling 2 Mini +26

Inkling 2 Mini 57

Model card 17, no knowledge cut-off. Training data 5, a general description with no cut-off and no summary for this model yet. Last change 20, uploaded today. Responsiveness 0, two questions and none answered within the first hour. Version policy 5, a first release. File health 10, the files and the card agree. 17 + 5 + 20 + 0 + 5 + 10 = 57.

Qwen3-Coder-30B-A3B-Instruct 31

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, languages and a knowledge cut-off aren't. Training data 5, the blog describes the mix in general terms without a cut-off. Last change 5, config.json was corrected on 3 December 2025, 336 days before the 4 November 2026 check. Responsiveness 0, counted by script on 4 November, none of 26 discussions has a reply from Alibaba's Qwen staff, and the one Hub-flagged member who replied is the independent quantiser bartowski. Version policy 5, a first release. File health 5, the files now agree with the card, but reports about the parser and an attention error wait without a reply. 11 + 5 + 5 + 0 + 5 + 5 = 31.

Risk Inkling 2 Mini +15

Inkling 2 Mini 70

File safety 25, safetensors only and no repository code to run. Provenance 15, the files are in the organisation Thinking Machines links to, with a SHA-256 on every LFS file. Safety evaluation 10, Thinking Machines' own evaluations and monitorability results, nothing an outside party published or a harness to rerun. Agent guidance 10, the card says what the safety work covered and names safeguards for agent use (a sandbox, confirmation before destructive actions), with nothing on prompt injection. Licence risk 5, 10 off for a use policy that reaches beyond the law and that can change at any time. Security 5, security.txt and a disclosure policy. 25 + 15 + 10 + 10 + 5 + 5 = 70.

Qwen3-Coder-30B-A3B-Instruct 55

File safety 25, safetensors weights, and the shipped parser script runs neither to load the model nor to build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards, though it's sold for agents that run commands. Licence risk 15, plain Apache 2.0 that hasn't changed. Security programme 0, no security.txt, disclosure policy or security contact for Qwen was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent. Files unchanged on 4 November, and QwenLM/Qwen3-Coder still has no SECURITY.md. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Agent interface Inkling 2 Mini +10

Inkling 2 Mini 85

Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, tml-renderers renders and parses it, and vLLM and SGLang name their parsers. Trained tool calling 20, several calls in one turn. Structured output 0, not documented. Reasoning control 10, reasoning_effort per request. Context 10, 1M trained. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Qwen3-Coder-30B-A3B-Instruct 75

Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, the card shows how tools are declared, the README names the parser for SGLang and vLLM, and the repository ships it. Trained tool calling 20, the template renders several calls a turn and the training used agent reinforcement learning. Structured output 0, not documented. Reasoning control 0, the model has no thinking. Context 10, 262,144 tokens native, with the YaRN extension not counted. Template, parser and config unchanged on 4 November. 20 + 25 + 20 + 0 + 0 + 10 = 75.

Score by category

CategoryWeightInkling 2 MiniQwen3-Coder-30B-A3B-InstructEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%6090Qwen3-Coder-30B-A3B-Instruct +30
Risk20%7055Inkling 2 Mini +15
Agent interface10%8575Inkling 2 Mini +10
Documentation and upkeep10%5731Inkling 2 Mini +26
Negative events≤1500
TotalC 61/100C 55.7/100

Facts side by side

FactInkling 2 MiniQwen3-Coder-30B-A3B-Instruct
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabAlibaba (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-11-202025-12-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/5 (4)

Verdicts

Inkling 2 Mini

Thinking Machines' small open model, a looped 26.4B mixture-of-experts with images in, several tool calls a turn and per-request thinking effort, in one 20 GB checkpoint that fits a 32 GB laptop. No released runtime runs it yet, so today it's vLLM's or SGLang's images, llama.cpp from master, or Tinker.

Qwen3-Coder-30B-A3B-Instruct

A coding model 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 under Apache 2.0, and several providers host it. It runs commands for agents with no safety results or prompt-injection guidance, and Alibaba hasn't answered its discussions.

Before you call either

Inkling 2 Mini

  1. No released runtime runs it yet. Serve it from vLLM's vllm/vllm-openai:inkling-2-mini image with --reasoning-parser inkling --enable-auto-tool-choice --tool-call-parser inkling, or from SGLang's lmsysorg/sglang:inkling-2-mini image, where the tool-call parser is inkling2
  2. On a laptop, ggml-org's GGUF runs in a llama.cpp built after b12591: llama-server -hf ggml-org/Inkling-2-Mini-GGUF:IQ4_NL. The looped architecture isn't in a llama.cpp release yet
  3. Pass reasoning_effort as none, minimal, low, medium, high (the default), xhigh or max, or a number from 0 to 0.99. The minimum doesn't fully turn reasoning off
  4. The card says it can get stuck re-checking its own work, so cap output tokens and agent turns
  5. Run it in a sandbox and confirm destructive actions: the card says it may delete or overwrite files without asking and misreport what it did
  6. Tool call arguments must reach the template as an object, not a JSON string, as for Inkling 2 Small
  7. Images should be 40 to 4096 px a side. It takes no audio, and the template raises an error for an audio part
  8. Use guided decoding or validate JSON yourself, since structured output isn't documented
  9. Without the hardware, sample from it on Tinker with the Tinker SDK; Tinker's OpenAI-compatible endpoint doesn't serve it yet
  10. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

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, Inkling 2 Mini or Qwen3-Coder-30B-A3B-Instruct?

Inkling 2 Mini scores 61 (C) on agent readiness against Qwen3-Coder-30B-A3B-Instruct's 55.7 (C), and leads in 3 of 4 scored categories. Qwen3-Coder-30B-A3B-Instruct leads on reach.

Other comparisons with Inkling 2 Mini 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.