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

Cola2 vs Qwen3.5-9B

Qwen3.5-9B scores 60.5 (C) on agent readiness against Cola2's 33.9 (F), and leads in 3 of 4 scored categories. Cola2 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 6359 open weights comparisons

Which one, for what

Cola2 F

Best for Researchers working on latent or diffusion language models who want a checkpoint to study

Ahead on

  • Documentation and upkeep, 58 against 34

Watch for

No licence stated for the weights

Qwen3.5-9B C

Best for Agents that want a small multimodal tool-calling model on a laptop or a 16 GB GPU, under a plain licence

Ahead on

  • Reach, 85 against 25
  • Risk, 55 against 40
  • Agent interface, 70 against 20

Watch for

No quantised build from Qwen itself

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.5-9B +60

Cola2 25

Memory 15, the only build is the F32 safetensors set, 35.07 GB, and 35.07 GB × 1.2 = 42.1 GB, within 64 GB. Loaded as BF16, as the card's example does, it needs about half, but the line reads the file size. Runtimes 0, none of the six runs it in a released version. Builds 0, one set of weights and no quantised build. Terms 0, no licence for the weights. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it, and nothing names an API that serves it. 15 + 0 + 0 + 0 + 10 + 0 = 25.

Qwen3.5-9B 85

Memory 30, Qwen publishes no quantised 9B, so the smallest 4-bit build from a runtime's own library is Ollama's qwen3.5:9b at 6.6 GB, about 7.9 GB with the fifth added, well under 16 GB. Runtimes 25, the cap, with vLLM listed in its stable docs, Transformers at released tags, llama.cpp, Ollama's library, LM Studio's own catalogue and SGLang all running the architecture. Builds 0, Qwen's FP8 and GPTQ repositories cover only the 27B and larger Qwen3.5 models, so every quantisation of the 9B is someone else's. Terms 15, plain Apache 2.0. Download 10, the repository isn't gated. Hosted 5, Together, Featherless AI, OVHcloud and DeepInfra are live for it on its Hugging Face page. 30 + 25 + 0 + 15 + 10 + 5 = 85.

Agent interface Qwen3.5-9B +50

Cola2 20

Chat template 20, A chat template in tokenizer_config.json (4,116 characters), which came with the Qwen3 tokenizer. Tool-calling format 0, none. Trained tool calling 0, not trained for tool calling. Structured output 0, Nothing about JSON or schema-constrained output. Reasoning control 0, no reasoning mode. Context 0, no context length is stated. 20 + 0 + 0 + 0 + 0 + 0 = 20.

Qwen3.5-9B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10, the card names the qwen3_coder parser for vLLM and SGLang but leaves the declaration and return format to the template, and Qwen's own function-calling guide still describes Qwen3's Hermes format. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, nothing documents asking the weights for JSON. Reasoning control 10, thinking turns off per request with enable_thinking false and the reasoning comes back in think tags that the qwen3 parser splits out. Context 10, 262,144 tokens native.

Documentation and upkeep Cola2 +24

Cola2 58

Model card 8, Intended use and limitations (the out-of-scope list, and the unconverged latent model) and the architecture are on the card and the GitHub model card it links. Training data 15, the GitHub model card names the source (OLMo 2 pretraining text, retokenised) and the mix by stage with token counts, 346.03B in all. Last change 20, All six commits are from 6 November 2026, four days before this check, the last one updating a checksum in the README. Responsiveness 0, no discussions on the repository, so nobody has asked anything yet and the line reads as none answered, as settled in calibration. Version policy 5, A first release. File health 10, Config, files and card agree: F32 weights, a float32 config and a card that says to load them as bfloat16, with SHA256SUMS to check the download. 8 + 15 + 20 + 0 + 5 + 10 = 58.

Qwen3.5-9B 34

Model card 14, it covers intended use, architecture, parameters, context and 201 languages but gives no limitations and no knowledge cut-off. Training data 5, a general line about trillions of multimodal tokens with no cut-off. Last change 5, the files and card last changed on 2 March 2026 (c202236), 247 days before 4 November, within a year. Responsiveness 0, no Qwen member replied in any of the 40 most recent of the 45 discussions that aren't pull requests (2 March to 29 September 2026). Version policy 5, a first release that was never replaced in place, with no dated notes across generations. File health 5, two reports about the files and card (15 and 51) are still open with no reply. 14 + 5 + 5 + 0 + 5 + 5 = 34. The card's highlights mention sparse Mixture-of-Experts for the series while this 9B is dense, but its own overview matches config.json, so it's not counted as a contradiction.

Risk Qwen3.5-9B +15

Cola2 40

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the ByteDance-Seed organisation, which the ByteDance-Seed GitHub repository for the model links to (10). Safety evaluation 0, no safety results. Agent guidance 5, General cautions in the GitHub model card: not instruction-tuned or safety-aligned, not for use as an assistant, for facts or advice, or for high-impact decisions about people. Licence risk 0, With no licence for the weights there is nothing to hold ByteDance to. Security programme 5, the GitHub repository's SECURITY.md sends reports to ByteDance's security centre and says how they're assessed (5). 15 + 15 + 0 + 5 + 0 + 5 = 40.

Qwen3.5-9B 55

File safety 25, safetensors only and nothing from the repository runs on load or to build prompts. Provenance 15, the Qwen organisation linked from Alibaba's QwenLM README, with a SHA-256 for every shard. Safety evaluation 0, none on the card, and the Qwen3.5 blog couldn't be read, so this is couldn't check scored as absent. Agent guidance 0, the card has no prompt-injection guidance, refusal scope or cautions. Licence risk 15, Apache 2.0 with nothing added and a working licence link. Security programme 0, no SECURITY.md in Qwen's GitHub repositories, no security.txt on qwen.ai or alibabacloud.com, and whether Alibaba's group security centre takes reports about Qwen models couldn't be checked.

Score by category

CategoryWeight this runCola2Qwen3.5-9BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%252585Qwen3.5-9B +60
Risk20%204055Qwen3.5-9B +15
Agent interface10%102070Qwen3.5-9B +50
Documentation and upkeep10%105834Cola2 +24
Negative events≤1500
TotalF 33.9/100C 60.5/100

Facts side by side

FactCola2Qwen3.5-9B
KindOpen-weight modelOpen-weight model
VendorByteDance (Seed)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceNone stated for the weights (the code is Apache 2.0)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-062026-03-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.5/5 (4)

Verdicts

Cola2

A research release, and an honest one: ByteDance Seed says it's a base model with an unconverged latent stage, scoring below Llama-3-8B on its own table. It's here for people studying continuous-latent generation. Agents can't use it as a model: 32-token completions, no chat or tools, the repository's own code to load it, and no licence on the weights.

Qwen3.5-9B

A small dense vision-language model with trained tool calling, thinking that turns off per request and a 262,144-token context. Ollama's 4-bit build is 6.6 GB and the BF16 files 19.3 GB, and every major runtime loads it. The files haven't changed since 2 March 2026, Qwen answered none of the 40 latest discussions, and no safety results are published.

Before you call either

Cola2

  1. Don't plan to use this as your model. It completes short prompts and wasn't tuned to follow instructions
  2. Don't use it commercially on the strength of this listing. The weights have no stated licence
  3. If you study it, read modeling_cola2.py first: trust_remote_code runs it
  4. Pin Transformers below 5, as the card requires
  5. Pass a seeded torch.Generator to generate(). Output varies between runs even with greedy decoding
  6. Check the download with sha256sum -c SHA256SUMS

Qwen3.5-9B

  1. Smallest start is ollama run qwen3.5:9b (6.6 GB, q4_k_m)
  2. On vLLM run vllm serve Qwen/Qwen3.5-9B --port 8000 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, or tool calls come back as text
  3. Tool calls use the XML style <tool_call><function=name><parameter=x>, not Hermes JSON, so use the qwen3_coder parser and not hermes
  4. Thinking is on by default; pass chat_template_kwargs with enable_thinking false for short tasks, since /nothink isn't supported
  5. There's no generation_config.json, so pass sampling yourself, temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5 when thinking, or 0.7, 0.8, 20, 1.5 without
  6. Keep at least 128K of context when thinking, and turn on YaRN only beyond 262,144 tokens
  7. Validate JSON output yourself or use the runtime's guided decoding

Questions

Which is better for AI agents, Cola2 or Qwen3.5-9B?

Qwen3.5-9B scores 60.5 (C) on agent readiness against Cola2's 33.9 (F), and leads in 3 of 4 scored categories. Cola2 leads on documentation and upkeep.

Other comparisons with Cola2 or Qwen3.5-9B

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.