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

Cola2 vs MiniMax-M2.7

MiniMax-M2.7 scores 57.6 (C) on agent readiness against Cola2's 33.9 (F), and leads in 2 of 4 scored categories. Cola2 leads on risk and 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

  • Risk, 40 against 30
  • Documentation and upkeep, 58 against 42

Watch for

No licence stated for the weights

MiniMax-M2.7 C

Best for Researchers and personal projects with a 4 to 8 GPU server who want an open agent and coding model with parallel tool calls

Ahead on

  • Reach, 60 against 25
  • Agent interface, 75 against 20

Watch for

Commercial use needs MiniMax's written authorisation since a licence swap on 11 April 2026, made without a note

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.

Agent interface MiniMax-M2.7 +55

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.

MiniMax-M2.7 75

The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 25, as MiniMax's own guide documents how tools go in and how calls come back, gives a parsing function, and its deployment guides name the vLLM and SGLang parsers. Trained tool calling earns 20, with several invoke blocks in one call. Structured output earns nothing, since JSON output isn't documented or claimed. Reasoning control earns nothing, because thinking is always on with no documented way to turn it off or budget it. Context earns 10 for 204,800 tokens in the config with no position scaling.

Reach MiniMax-M2.7 +35

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.

MiniMax-M2.7 60

Memory earns 5. MiniMax only publishes its 230 GB FP8 release, and the smallest build of 4-bit or better from a runtime's own library is LM Studio's Q4_K_M GGUF at 138.3 GB, about 166 GB with the fifth added, so it needs more than our 107.4 GB machine and fits within 256 GB. Runtimes earn the full 25, with model code in released vLLM, SGLang, llama.cpp and Transformers, an LM Studio catalogue entry, and Ollama 0.40.14, whose pinned llama.cpp b11963 has the minimax-m2 architecture (capped at 25). Builds earn 10 for one publisher precision, the FP8 release. Terms earn 5, since the licence today allows only personal, research and non-profit use without MiniMax's written authorisation. Download earns 10, with no gate or account. Hosted earns 5, since Novita, Featherless AI and DeepInfra serve it through Hugging Face, while MiniMax's own API is closed to new users and retires it on 18 November 2026.

Documentation and upkeep Cola2 +16

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.

MiniMax-M2.7 42

The model card earns 2, stating only intended use and leaving out limitations, architecture, parameters, context, natural languages and a cut-off. Training data earns nothing, since only the training process is described. The last change earns 20, a card commit on 26 October 2026 that renames a MiniMax Agent link to MiniMax Code, 9 days before this check; the files, template and code last changed on 20 April 2026. Responsiveness earns 10, with a MiniMax reply in 8 of 36 discussions, none since June. Version policy earns 5, since earlier and later models sit in their own repositories without dated notes. File health earns 5, because a report that it doesn't load in Transformers v5 waits without a reply.

Risk Cola2 +10

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.

MiniMax-M2.7 30

File safety earns 15, safetensors only with no pickle files, less 10 because every documented loading route passes trust_remote_code for the repository's Python. Provenance earns the full 15, files in the organisation MiniMax links to with a SHA-256 for each shard. Safety evaluation and agent guidance earn nothing, as MiniMax publishes neither. Licence risk earns nothing (read 21 October 2026). The Prohibited Uses appendix goes beyond the law, MiniMax swapped a commercial licence for a non-commercial one two days after release, and neither that swap nor the amendment three days later carries a dated note. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or advisories.

Score by category

CategoryWeight this runCola2MiniMax-M2.7Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%252560MiniMax-M2.7 +35
Risk20%204030Cola2 +10
Agent interface10%102075MiniMax-M2.7 +55
Documentation and upkeep10%105842Cola2 +16
Negative events≤1500
TotalF 33.9/100C 57.6/100

Facts side by side

FactCola2MiniMax-M2.7
KindOpen-weight modelOpen-weight model
VendorByteDance (Seed)MiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceNone stated for the weights (the code is Apache 2.0)MiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation)
Read-only variant documentednono
llms.txtnono
Last release2026-11-062026-04-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone1.8/5 (4)

How the scores have moved

Cola2

No score change since it was listed.

MiniMax-M2.7

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.

MiniMax-M2.7

A 230B mixture-of-experts model for coding and agent harnesses, with parallel tool calls, about 200K of context and parsers in vLLM and SGLang. It needs a 4 GPU server for FP8 or about 166 GB for a 4-bit library build, and it always thinks. The main risk is the licence, switched to non-commercial two days after release.

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

MiniMax-M2.7

  1. Check the use is personal, research or non-profit before starting it; anything commercial needs MiniMax's written authorisation, and commercial users must show Built with MiniMax M2.7
  2. Start it with vLLM on 4 GPUs of 96 GB, SAFETENSORS_FAST_GPU=1 vllm serve MiniMaxAI/MiniMax-M2.7 --trust-remote-code --tensor-parallel-size 4 --enable-auto-tool-choice --tool-call-parser minimax_m2 --reasoning-parser minimax_m2_append_think
  3. In SGLang use --tool-call-parser minimax-m2 and --reasoning-parser minimax-append-think, with --trust-remote-code
  4. MiniMax's guides budget 220 GB for the weights and 240 GB per 1M tokens of KV cache, with 196K the most per sequence
  5. On one large-memory machine, LM Studio's catalogue entry minimax/minimax-m2.7 lists a 138 GB Q4_K_M GGUF and states 138 GB minimum memory
  6. Sample with temperature 1.0, top_p 0.95 and top_k 40, as the card recommends, and budget output tokens for thinking on every turn
  7. Pin Transformers 4.57.1 as MiniMax's guide does; a report that it fails on Transformers v5 has no answer
  8. Without the hardware, call it through Novita, Featherless AI or DeepInfra; MiniMax's own API retires M2.7 on 18 November 2026

Questions

Which is better for AI agents, Cola2 or MiniMax-M2.7?

MiniMax-M2.7 scores 57.6 (C) on agent readiness against Cola2's 33.9 (F), and leads in 2 of 4 scored categories. Cola2 leads on risk and documentation and upkeep.

Other comparisons with Cola2 or MiniMax-M2.7

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.