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

Cola2 vs Gemma 4 12B IT

Gemma 4 12B IT scores 72.3 (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 12B IT BB

Best for Agents on a 12 GB or larger GPU or Mac that want a permissively licensed tool-calling model with images, audio and long context

Ahead on

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

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No safety evaluation figures 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 12B 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 12B IT 95

Memory 30, Google's own 4-bit QAT GGUF with its projector is 7.15 GB, which with a fifth on top is 8.6 GB and fits in 16 GB or less. Runtimes 25, released support in Transformers, vLLM, SGLang, llama.cpp, Ollama and LM Studio, six of six, all for the separate gemma4_unified architecture. Builds 15, Google publishes a Q4_0 GGUF and a w4a16 build, read as two kinds as for the 31B. Terms 15, plain Apache 2.0 with nothing added. Download 10, no account or gate. Hosted 0, the Gemini API serves only the two largest sizes and no inference provider lists this one.

Agent interface Gemma 4 12B 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 12B IT 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, Google documents how tools are declared and how calls come back, and ships a response schema for Transformers' parser. Trained tool calling 20, several calls in one turn. Structured output 0, nothing documents how to ask the weights for JSON or a schema. Reasoning control 10, thinking is off by default, turned on per request, and returned in a thought channel. Context 10, 262,144 tokens native.

Risk Gemma 4 12B 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 12B IT 70

File safety 25, safetensors and GGUF only, with nothing from the repository run on load. Provenance 15, the files sit in Google's own organisation and every file has a checksum. Safety evaluation 0, the card says testing showed minimal policy violations but gives no figures. Agent guidance 10, the card names the harm categories its safety training covers and asks for content-safety safeguards, and the tool guide says to validate calls, with no prompt-injection guidance. Licence risk 15, Apache 2.0 with no added policy, no threshold and a working link. Security programme 5, Google's security.txt and reward programme give a route to report a flaw, but no public Gemma advisories were found.

Documentation and upkeep Gemma 4 12B IT +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.

Gemma 4 12B IT 85

Model card 20, all seven items are there. Training data 10, a general description by type with a January 2025 cut-off and the filtering, but no sources, mix or sizes. Last change 20, Google merged a fix for 210 glitch tokens in tokenizer.json on 30 October 2026, two days before 1 November. Responsiveness 20, Google replied to 18 of 34 questions and reports, the last on 2026-07-31, re-counted on 1 November. Version policy 10, earlier Gemma generations keep their own repositories and gemma.ai has a dated releases page. File health 5, the files agree with the card but a report about them waits without a reply.

Score by category

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

Facts side by side

FactCola2Gemma 4 12B 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)

How the scores have moved

Cola2

No score change since it was listed.

Gemma 4 12B IT

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 12B IT

A mid-size cousin for agent work with tools, optional thinking and image and audio input, under Apache 2.0. Google's 4-bit build needs under 9 GB with working space, so it runs on a 12 GB GPU or any recent Mac in all the common runtimes. The main risks are no published safety results and no documented JSON output.

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 12B IT

  1. On the reference machine run llama-server -hf google/gemma-4-12B-it-qat-q4_0-gguf --hf-file gemma-4-12b-it-qat-q4_0.gguf --jinja -c 131072, and add --mmproj with mmproj-gemma-4-12b-it-qat-q4_0.gguf for images and audio
  2. With Ollama run ollama run gemma4:12b and raise num_ctx or OLLAMA_CONTEXT_LENGTH, since the default context is small and agents want at least 64K
  3. In vLLM or SGLang pass --tool-call-parser gemma4 --reasoning-parser gemma4 (vLLM also --enable-auto-tool-choice), or tool calls come back as text; Google's w4a16 build is the 4-bit route there
  4. Thinking is off by default; pass enable_thinking=True or start the system prompt with <|think|>, and drop earlier turns' thinking from history except on tool-call turns
  5. Put images before the text and audio after it, keep audio to 30 seconds and video to 60 frames, and validate tool names and arguments before running them
  6. Transformers needs 5.10.0 or later for gemma4_unified, and mlx-lm has no gemma4_unified code, so on a Mac use mlx-vlm, LM Studio or Ollama

Questions

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

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

Other comparisons with Cola2 or Gemma 4 12B 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.