Cola2 vs Qwen3-Coder-Next

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-Coder-Next 85

Memory earns 15 of 30, since Alibaba's own Q4_K_M GGUF is 48.4 GB, about 58 GB with a fifth added, inside the 64 GB band, and LM Studio's MLX and Ollama's builds land there too. Runtimes reach the 25 cap on released vLLM (v0.33.0), SGLang (v0.5.23), llama.cpp, Ollama (its library entry, and llama.cpp b11963 pinned by Ollama 0.40.14 has qwen3next), LM Studio and Transformers. Alibaba's FP8 and GGUF builds give builds 15. The Apache 2.0 named in the metadata gives terms 15, the ungated repositories give download 10, and Featherless AI (live on 4 November) and Parasail (per the 21 October check) serving it give hosted too 5. 15+25+15+15+10+5 = 85.

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-Coder-Next 75

The template ships in the repository (20). Tool calling is the model's strength, and Alibaba documents how tools are declared, names and ships the qwen3_coder parser and describes the format in its report (25), with several calls per turn in a model trained on 21 harness formats (20). Context is 262,144 tokens native (10). Structured output scores 0, as nothing documents JSON output, and reasoning control scores 0 because the model has no thinking mode to control.

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-Coder-Next 41

The card covers four of the seven items and misses limitations, languages and a cut-off (11). The technical report names the data sources, the cut-off and the filtering with some sizes (15). The files last changed on 3 February 2026 (4 February in the GGUF repository), 274 days ago, within a year (5). Alibaba's staff answered none of the 40 discussions; the one reply from a Qwen organisation member is not the publisher's (0), and GitHub issues couldn't be counted. It's a first release (5), and reports of a broken shipped parser and the missing licence wait unanswered (5). 11+15+5+0+5+5 = 41.

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-Coder-Next 50

Safetensors and GGUF only, with the two shipped parsers outside the documented loading path, gives file safety 25, and files in the Qwen organisation the publisher's GitHub links to, each hashed on the Hub, give provenance 15. Licence risk loses 5 because the card's licence link is broken and no LICENSE file exists anywhere. Safety evaluation, agent guidance and a security programme score 0, since the report's cybersecurity appendix measures skills rather than safe behaviour, nothing guides agent use and no reporting route was found.