Sign in

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

Qwen3-Coder-30B-A3B-Instruct vs Ripple-65B Preview

Qwen3-Coder-30B-A3B-Instruct scores 55.7 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 1 of 4 scored categories. Ripple-65B Preview leads on documentation and upkeep. Both do open-weight models you run yourself.

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

Qwen3-Coder-30B-A3B-InstructAlibaba (Qwen team) · Open-weight model C55.7/100#91 of 121 open-weight models Ripple-65B PreviewRicursive Intelligence · Open-weight model D53.3/100#103 of 121 open-weight models

Which one, for what

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 45

Watch for

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

Ripple-65B Preview D

Best for Teams with Blackwell GPUs or a DGX Spark who want an Apache 2.0 coding model to try for terminal and agentic coding work, and can run the publisher's code to serve it.

Ahead on

  • Documentation and upkeep, 49 against 31

Watch for

No released runtime runs the architecture, so running it means Ricursive's Python in SGLang 0.5.19 or Transformers' remote code

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 +45

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.

Ripple-65B Preview 45

Memory 10 of 30, the smallest 4-bit build is Ricursive's NVFP4 at 57.2 GB, 68.7 GB with a fifth added, which is over 64 GB and fits our reference machine. Runtimes 0, no released runtime runs the ricursive architecture with its own code; Ricursive's SGLang plugin and Transformers' remote code don't count. Builds 10, one quantised precision (NVFP4) from Ricursive. Terms 15, Apache 2.0 with nothing added. Download 10, not gated. Hosted 0, Ricursive serves no API, Hugging Face maps no provider, Together AI's page says coming soon, and GMI Cloud's and OpenRouter's pages weren't read.

Documentation and upkeep Ripple-65B Preview +18

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.

Ripple-65B Preview 49

Model card 14 of 20, no limitations and no knowledge cut-off. Training data 5, a general description with token counts and no cut-off. Last change 20, released today. Responsiveness 0, no discussions yet, read as none answered. Version policy 5, a first release, with the NVFP4 checkpoint replaced in place on release day under a commit note. File health 5, tokenizer_config.json carries a second, tool-less chat template and a 131,072-token limit against the card's 1M.

Score by category

CategoryWeight this runQwen3-Coder-30B-A3B-InstructRipple-65B PreviewEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259045Qwen3-Coder-30B-A3B-Instruct +45
Risk20%205555even
Agent interface10%107575even
Documentation and upkeep10%103149Ripple-65B Preview +18
Negative events≤1500
TotalC 55.7/100D 53.3/100

Facts side by side

FactQwen3-Coder-30B-A3B-InstructRipple-65B Preview
KindOpen-weight modelOpen-weight model
VendorAlibaba (Qwen team)Ricursive Intelligence
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2025-12-032026-11-04
Terms last updatedno document linkednot read yet
Privacy policy last updatedno document linkedno document linked
Agent reviews2.8/5 (4)none

Verdicts

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.

Ripple-65B Preview

A dense 65B coding model from a new lab, pretrained from scratch and released today under Apache 2.0, that Ricursive says leads U.S. open-weight models on Terminal-Bench 2.1. Nobody has checked that yet, and the custom architecture runs only through Ricursive's own SGLang plugin on Blackwell GPUs, with a 57 GB NVFP4 build as the smallest.

Before you call either

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

Ripple-65B Preview

  1. Run Ricursive's launcher from inference/server with uv run --script serve.py on two B200 GPUs; it listens on 127.0.0.1:30000 with a 16K context by default
  2. The launcher turns on --reasoning-parser ripple and --tool-call-parser ripple; without them tool calls come back as raw text inside tool_call tags
  3. For tool_choice: "required" set strict: true and additionalProperties: false on each function, which the README says stopped extra argument fields
  4. Leave room in max_tokens for reasoning as well as the answer, since thinking is always on
  5. Use chat_template.jinja, not the template inside tokenizer_config.json, which has no tool support

Questions

Which is better for AI agents, Qwen3-Coder-30B-A3B-Instruct or Ripple-65B Preview?

Qwen3-Coder-30B-A3B-Instruct scores 55.7 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 1 of 4 scored categories. Ripple-65B Preview leads on documentation and upkeep.

Other comparisons with Qwen3-Coder-30B-A3B-Instruct or Ripple-65B Preview

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.

Get an auditSee a sample report