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

Cola2 vs Gemma 4 31B IT

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against Cola2's 33.9 (F), and leads in every scored category. 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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No licence stated for the weights

Gemma 4 31B IT BB

Best for An agent with a 24 GB GPU or more that wants a dense multimodal cousin with tool calling under a plain licence

Ahead on

  • Reach, 95 against 25
  • Risk, 70 against 40
  • Agent interface, 85 against 20
  • Documentation and upkeep, 65 against 58

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No safety evaluation results published

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 Gemma 4 31B IT +70

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.

Gemma 4 31B IT 95

Memory 25, Google's own QAT Q4_0 GGUF is 17.7 GB, which with a fifth added comes to about 21 GB and fits a 24 GB card even with the vision projector. Runtimes 25, released code in llama.cpp, Ollama's library, vLLM, SGLang and Transformers fills the cap without LM Studio, which only Google's guides name. Builds 15, Google ships a 4-bit GGUF and a 4-bit compressed-tensors build, read as two of the kinds the checklist names. Terms 15, plain Apache 2.0 with nothing added. Download 10, no gate and no account. Hosted 5, Google's Gemini API serves it today.

Agent interface Gemma 4 31B IT +65

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.

Gemma 4 31B IT 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, Google documents the declaration and call syntax and ships a response schema that Transformers parses. Trained tool calling 20, several calls and responses in one turn. Structured output 0, Google documents none and the card doesn't claim it. Reasoning control 10, thinking turns on or off per request and comes back in its own block. Context 10, 262,144 tokens native.

Risk Gemma 4 31B IT +30

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.

Gemma 4 31B IT 70

File safety 25, safetensors only and no code from the repository runs to load it or build prompts. Provenance 15, the files come from the google organisation that gemma.ai links to, with a SHA-256 for every weight file and a git hash for every file. Safety evaluation 0, Google says violations were minimal but publishes no results. Agent guidance 10, the card says what its safety training covers and asks for content safeguards, and the tool guide says to validate calls, but there is no prompt-injection guidance. Licence risk 15, Apache 2.0 carries none of the deductions and its link works. Security programme 5, Google's company-wide security.txt and reward programme exist but nothing ties them to Gemma, and no public advisories were found.

Documentation and upkeep Gemma 4 31B IT +7

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.

Gemma 4 31B IT 65

Model card 20, all seven items are there, with languages given as counts. Training data 10, a general description with a January 2025 cut-off. Last change 10, the files last changed on 20 July, 104 days before 1 November, and Google's reference code for Gemma 4 last changed in a way that runs this model on 6 July, both inside 180 days. Responsiveness 10, Google answered 14 of the last 40 discussions, none since 30 July. Version policy 10, earlier generations are kept in their own repositories with dated releases. File health 5, two template reports wait without a reply.

Score by category

CategoryWeight this runCola2Gemma 4 31B ITEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%252595Gemma 4 31B IT +70
Risk20%204070Gemma 4 31B IT +30
Agent interface10%102085Gemma 4 31B IT +65
Documentation and upkeep10%105865Gemma 4 31B IT +7
Negative events≤1500
TotalF 33.9/100BB 74.1/100

Facts side by side

FactCola2Gemma 4 31B IT
KindOpen-weight modelOpen-weight model
VendorByteDance (Seed)Google DeepMind
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.txtnoyes
Last release2026-11-062026-07-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3.8/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.

Gemma 4 31B IT

A dense multimodal cousin with documented tool calling, optional thinking and a 256K context, for general agent work and image reading on one 24 GB GPU through Google's 4-bit build. It runs in every major runtime under plain Apache 2.0. The main risk is that Google publishes no safety results and has gone quiet on the repository since July.

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

Gemma 4 31B IT

  1. On the reference machine run llama-server -hf google/gemma-4-31B-it-qat-q4_0-gguf --hf-file gemma-4-31B_q4_0-it.gguf --jinja -c 32768, adding gemma-4-31B-it-mmproj.gguf for images
  2. Or ollama run gemma4:31b for the 20 GB Q4_K_M build
  3. In vLLM serve with --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4, as vLLM's recipe does
  4. Thinking is off by default, so pass enable_thinking: true in chat_template_kwargs to turn it on, and expect the reasoning in the thought channel block
  5. Drop earlier thoughts from the history except on tool-call turns, as the card asks
  6. Use the card's sampling, temperature 1.0, top_p 0.95, top_k 64
  7. Validate function names and arguments before running a call, and check JSON output yourself or use the runtime's guided decoding
  8. The w4a16 build relies on Marlin INT4 kernels that vLLM marks unsupported on AMD, so use the GGUF on the reference machine

Questions

Which is better for AI agents, Cola2 or Gemma 4 31B IT?

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against Cola2's 33.9 (F), and leads in every scored category.

Other comparisons with Cola2 or Gemma 4 31B IT

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.