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

DiffusionGemma 26B A4B IT vs North Mini Code 1.0

North Mini Code 1.0 scores 61 (C) on agent readiness against DiffusionGemma 26B A4B IT's 51.3 (D), and leads in 2 of 4 scored categories. DiffusionGemma 26B A4B IT 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

DiffusionGemma 26B A4B IT D

Best for Agents with about 64 GB of GPU memory that want fast single-user generation from text and images and can accept lower quality than Gemma 4

Ahead on

  • Risk, 70 against 60
  • Documentation and upkeep, 60 against 36

Watch for

No quantised build from Google, so the smallest official build needs the 64 GB band

North Mini Code 1.0 C

Best for Developers who want a coding agent on their own GPU with a permissive licence

Ahead on

  • Reach, 85 against 55
  • Agent interface, 85 against 70

Watch for

No limitations, safety results, languages or data description on the card

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 North Mini Code 1.0 +30

DiffusionGemma 26B A4B IT 55

Memory earns 15 because the only Google build is 51.7 GB of BF16, about 62 GB with the fifth added, which needs the 64 GB band. Runtimes get 15 for Transformers from 5.11.0, SGLang from v0.5.22 and vLLM, whose releases from v0.24.0 (tag commit 28 June 2026) to v0.33.0 register DiffusionGemmaForBlockDiffusion; llama.cpp (b12114, and Ollama through its pin b11963) and LM Studio don't run it. Builds score 0 because Google publishes no quantised build, though others have published FP8, NVFP4, GGUF and 4-bit copies. Apache 2.0 with nothing added gives terms the full 15 and the ungated repository gives download the full 10. Hosted too scores 0, since no inference provider is mapped and the Gemini API doesn't serve it.

North Mini Code 1.0 85

Memory 25, the smallest build from Cohere is the w4a16 repository, 19.38 GB, and 19.38 GB × 1.2 = 23.3 GB, within 24 GB. Unsloth's GGUF isn't read for this line. Runtimes 20, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the cohere2_moe model, and llama.cpp b12242 has the cohere2moe architecture. Builds 15, Quantised builds from Cohere at two precisions, FP8 and 4-bit weights (w4a16), each in its own repository. Terms 15, Apache 2.0 in the metadata and on the card, an OSI licence with nothing added. Download 10, the Hub API reports gated false for the model and its builds 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. 25 + 20 + 15 + 15 + 10 + 0 = 85.

Documentation and upkeep DiffusionGemma 26B A4B IT +24

DiffusionGemma 26B A4B IT 60

The card covers all seven points (20), and the training data is a general description with a January 2025 cut-off (10). The files last changed on 15 July 2026, 112 days before this check (10). Google organisation members answered 10 of the 20 discussions (10). It's a first release (5). File health gets 5 because the diffusers scheduler config disagrees with the card's sampling settings, though the files on the documented path agree.

North Mini Code 1.0 36

Model card 11, Intended use, the architecture, the parameters and the context are on the card. Training data 0, the card gives the training method and nothing about the data. Last change 10, the main repository last changed on 15 June 2026 (outdated chat templates removed), 148 days before this check, and the draft model's repository on 29 July, 104 days. Responsiveness 0, none of the 11 most recent discussions that aren't pull requests (7 June to 6 November 2026) has a reply from a CohereLabs member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release, with each build in its own repository. File health 10, Config, template and card agree on the architecture, and the June commit that removed broken templates says so. 11 + 0 + 10 + 0 + 5 + 10 = 36.

Agent interface North Mini Code 1.0 +15

DiffusionGemma 26B A4B IT 70

The chat template is in the repository (20) and handles several tool calls in one turn, and the card names function calling as trained (20). The tool-calling format gets 10, since only the template and the shipped response schema say how tools work here and Google's tool-calling guide is for Gemma 4. Structured output scores 0, undocumented and rejected by SGLang. Thinking can be turned on or off per request with the reasoning in its own channel (10), and the context is 256K (10).

North Mini Code 1.0 85

Chat template 20, chat_template.jinja in the repository (12,397 characters). Tool-calling format 25, the card documents how tools are declared (JSON schema through the chat template), how the call and its thinking go back into the history and how results are appended, and names the cohere_command4 tool-call parser for vLLM, which released vLLM has. Trained tool calling 20, the card says the model was specifically trained with tool-use capabilities for agentic coding, with reinforcement learning on verifiable tasks, and the template renders every call in a turn with thinking between them. Structured output 0, JSON schema is for describing tools. Reasoning control 10, the template has a reasoning_effort setting, and the card names the cohere_command4 reasoning parser, which returns thinking apart from the answer. Context 10, 256K tokens per the card, with 64K of output, and 500,000 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Risk DiffusionGemma 26B A4B IT +10

DiffusionGemma 26B A4B IT 70

File safety gets the full 25, safetensors only and loaded by Transformers' own code and a Jinja template. Provenance gets 15 for files in Google's organisation with a hash for every file. Licence risk keeps 15 under plain Apache 2.0. Agent guidance gets 10 for the card's list of harm categories and its advice to add content-safety safeguards. Safety evaluation scores 0 because the card states improvements without figures. The security programme gets 5 for Google's security.txt, with no public advisories for Gemma.

North Mini Code 1.0 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in Cohere's verified CohereLabs organisation, which cohere.com links to per our other Cohere listings (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or safety section, and nothing on prompt injection, instruction priority or what the model refuses. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 5, Cohere's trust centre holds a responsible disclosure policy with a bug bounty, as recorded on our Cohere listings (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Score by category

CategoryWeight this runDiffusionGemma 26B A4B ITNorth Mini Code 1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255585North Mini Code 1.0 +30
Risk20%207060DiffusionGemma 26B A4B IT +10
Agent interface10%107085North Mini Code 1.0 +15
Documentation and upkeep10%106036DiffusionGemma 26B A4B IT +24
Negative events≤1500
TotalD 51.3/100C 61/100

Facts side by side

FactDiffusionGemma 26B A4B ITNorth Mini Code 1.0
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindCohere
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-07-152026-07-29
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

DiffusionGemma 26B A4B IT

A text diffusion model for fast low-concurrency local generation from text, images and video, with optional thinking and Gemma 4's tool format, under Apache 2.0. Google's BF16 files need about 62 GB, and it runs in Transformers, SGLang and vLLM. Google's own figures put it below Gemma 4 26B A4B, and Google labels it experimental.

North Mini Code 1.0

A coding agent model that fits one 24 GB GPU at 4 bits, trained for tool use, with a 256K context, Apache 2.0 and four released runtimes. It's a research release and reads like one: nothing on limitations, safety or data, the card's run instructions are out of date, and Cohere hasn't answered a question on the repository.

Before you call either

DiffusionGemma 26B A4B IT

  1. Serve it with sglang serve --model-path google/diffusiongemma-26B-A4B-it --dllm-algorithm Gemma4Renoise --trust-remote-code on SGLang v0.5.22 or later, then call /v1/chat/completions
  2. In Transformers, install transformers>=5.11.0 and load DiffusionGemmaForBlockDiffusion with dtype="auto"; generation_config.json already holds the recommended sampler
  3. Turn thinking on with enable_thinking=True in apply_chat_template or <|think|> at the start of the system prompt, read the reasoning between <|channel>thought and <channel|>, and drop it from history before the next turn
  4. Don't rely on temperature, top_p, logit_bias or JSON Schema in SGLang, which ignores or rejects them for this model; validate JSON yourself
  5. Streaming arrives one 256-token canvas at a time, not token by token
  6. Put images before text in the prompt, and pick an image token budget of 70 to 1,120 by how much detail the task needs

North Mini Code 1.0

  1. Serve it with vLLM 0.33.0 or later and --tool-call-parser cohere_command4 --reasoning-parser cohere_command4 --enable-auto-tool-choice, with cohere_melody installed
  2. Pass the model's thinking back with its tool calls on every turn. The card says results drop without it
  3. Describe tools in JSON schema and append tool results as a dictionary with the tool role
  4. Use temperature 1.0 and top_p 0.95
  5. For llama.cpp the GGUF files are Unsloth's or bartowski's conversions, not Cohere's
  6. It's text only. Don't send images

Questions

Which is better for AI agents, DiffusionGemma 26B A4B IT or North Mini Code 1.0?

North Mini Code 1.0 scores 61 (C) on agent readiness against DiffusionGemma 26B A4B IT's 51.3 (D), and leads in 2 of 4 scored categories. DiffusionGemma 26B A4B IT leads on risk and documentation and upkeep.

Other comparisons with DiffusionGemma 26B A4B IT or North Mini Code 1.0

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.