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

Cola2 vs Qwen3.6-35B-A3B

Qwen3.6-35B-A3B scores 62.7 (B) 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 31

Watch for

No licence stated for the weights

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

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

Watch for

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

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.6-35B-A3B +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.6-35B-A3B 85

Memory earns 20 because the smallest 4-bit build from a runtime's own library is Ollama's Q4_K_M at 23 GB, which comes to 27.6 GB with the fifth added, so it needs a 32 GB machine rather than a 24 GB one. Runtimes earn the full 25, since released llama.cpp, Ollama, vLLM, SGLang and Transformers all run the architecture. Builds earn 10 for Alibaba's one quantised build, FP8, with no 4-bit or GGUF from the publisher. Terms earn 15 for plain Apache 2.0, download earns 10 for ungated files, and hosted earns 5 because DeepInfra, Featherless AI and Scaleway serve it through Hugging Face.

Agent interface Qwen3.6-35B-A3B +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.6-35B-A3B 70

The chat template earns 20 as a Jinja file in the repository. The tool-calling format earns 10, because the card names the qwen3_coder parser but leaves the return format to the template. Trained tool calling earns 20, with several calls to a turn in the template. Structured output earns 0, as JSON output isn't documented for the model. Reasoning control earns 10, thinking off per request with enable_thinking and the reasoning returned in think tags for the qwen3 parser. Context earns 10 for 262,144 tokens native.

Documentation and upkeep Cola2 +27

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.6-35B-A3B 31

The model card earns 11, covering intended use, architecture, parameters and context but not limitations, languages or a cut-off. Training data earns 5 for a general description with no cut-off. The last change earns 5, a README edit on 24 April 2026, 192 days before this check, past 180 days and within a year, and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. Responsiveness earns 0, with no Qwen reply in the 40 most recent of 62 discussions that aren't pull requests, recounted on 2 November. Version policy earns 5, the earlier version kept in its own repository without a note. File health earns 5, the files agree but reports about tool calling and the template wait unanswered.

Risk Qwen3.6-35B-A3B +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.6-35B-A3B 55

File safety earns 25 for safetensors only, loaded by the runtimes' own code and a Jinja template with nothing run from the repository. Provenance earns 15, files in the Qwen organisation the publisher links and a hash for every file. Safety evaluation and agent guidance earn 0, since the card has neither safety results nor any guidance on refusals, injection or safeguards. Licence risk keeps all 15, as Apache 2.0 carries none of the four conditions and the late LICENSE file only wrote down what the card already said. The security programme earns 0, with no reporting route found on qwen.ai, the card or the GitHub repository, which is noted as unchecked for Alibaba's group-wide centre.

Score by category

CategoryWeight this runCola2Qwen3.6-35B-A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%252585Qwen3.6-35B-A3B +60
Risk20%204055Qwen3.6-35B-A3B +15
Agent interface10%102070Qwen3.6-35B-A3B +50
Documentation and upkeep10%105831Cola2 +27
Negative events≤1500
TotalF 33.9/100B 62.7/100

Facts side by side

FactCola2Qwen3.6-35B-A3B
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-04-16
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/5 (4)

How the scores have moved

Cola2

No score change since it was listed.

Qwen3.6-35B-A3B

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.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

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.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, Cola2 or Qwen3.6-35B-A3B?

Qwen3.6-35B-A3B scores 62.7 (B) 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.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.