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

Kolibri-1 vs Qwen3-Coder-Next

Kolibri-1 scores 61 (C) on agent readiness against Qwen3-Coder-Next's 57.6 (C), and leads in 3 of 4 scored categories. Qwen3-Coder-Next leads on reach. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

Kolibri-1 C

Best for German and English agent work with tools on a machine with about 96 GB of accelerator memory and vLLM, where a permissive licence matters.

Ahead on

  • Risk, 65 against 50
  • Agent interface, 90 against 75
  • Documentation and upkeep, 70 against 41

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.8 out of 5

Watch for

The smallest publisher build is FP8 at 78.8 GB, so it needs about 95 GB and won't fit a 64 GB machine

Qwen3-Coder-Next C

Best for Agents that want a local coding model for long tool-calling loops on a single 64 GB to 128 GB machine.

Ahead on

  • Reach, 85 against 60

Watch for

No LICENSE file anywhere and a broken licence link on the card

Score by category

CategoryWeight this runKolibri-1Qwen3-Coder-NextEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256085Qwen3-Coder-Next +25
Risk20%206550Kolibri-1 +15
Agent interface10%109075Kolibri-1 +15
Documentation and upkeep10%107041Kolibri-1 +29
Negative events≤1500
TotalC 61/100C 57.6/100

Facts side by side

FactKolibri-1Qwen3-Coder-Next
KindOpen-weight modelOpen-weight model
VendorAleph AlphaAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-192026-02-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.3/5 (4)2.8/5 (4)

Verdicts

Kolibri-1

Kolibri-1 is a German and English reasoning model with a documented tool-call format, switchable thinking and a 262,144-token context, under Apache 2.0. Aleph Alpha's FP8 build needs about 95 GB and runs on vLLM through its plugin, Transformers 5.20 or recent llama.cpp. The main risk is no published safety results or security contact, and few repository answers.

Qwen3-Coder-Next

A fast coding cousin for agent harnesses, with 3B active parameters and tool calling trained across many scaffold formats for Claude Code, Cline or Qwen Code loops. Alibaba's 4-bit GGUF needs about 58 GB, fitting one 64 GB machine, and two providers host it. The main risk is neglect, with no change since February, no replies and no safety results.

Before you call either

Kolibri-1

  1. Start it with pip install 'aleph-alpha-inference>=1' then vllm serve Aleph-Alpha/Kolibri-1 --kv-cache-dtype fp8 --reasoning-parser kolibri1 --tool-call-parser kolibri1 --enable-auto-tool-choice
  2. Without the kolibri1 tool-call parser and enable-auto-tool-choice, tool calls come back as text in tool_call tags
  3. The plugin supports one vLLM minor version, 0.29, so don't upgrade vLLM while it's installed
  4. Thinking is on by default at high effort. Pass reasoning_effort none or enable_thinking false in chat_template_kwargs for short tasks
  5. Recommended sampling is temperature 1.0, top_p 0.97 and top_k 128
  6. Past 262,144 tokens, add --max-model-len 1048576 and the max_position_embeddings override in --hf-overrides, though Aleph Alpha recommends staying at or below 262,144
  7. With Transformers 5.20 or later, tokenizer.parse_response returns the answer in content and the reasoning in thinking
  8. On the reference machine the FP8 build fits by size, but no document confirms vLLM runs FP8 on gfx1151, and Aleph Alpha ships no GGUF for llama.cpp
  9. Validate tool results in your own code, as the card asks

Qwen3-Coder-Next

  1. Quickest start is ollama run qwen3-coder-next (Q4_K_M, 52 GB of files)
  2. On our reference machine Alibaba's Q8_0 GGUF (84.8 GB, about 102 GB in use) also fits, run with llama-server -m Qwen3-Coder-Next-Q8_0/Qwen3-Coder-Next-Q8_0-00001-of-00004.gguf --jinja -ngl 99 -fa on -c 131072
  3. Serve with vllm serve Qwen/Qwen3-Coder-Next --enable-auto-tool-choice --tool-call-parser qwen3_coder (vLLM 0.15.0 or later), using the built-in parser rather than the repository's qwen3coder_tool_parser_vllm.py, which fails to import on newer vLLM per discussion 36
  4. The card's commands use tensor parallel 2 though the text says 4 GPUs, and it suggests cutting the context to 32,768 if the server fails to start
  5. There's no thinking mode, so don't pass enable_thinking or wait for reasoning_content
  6. Sampling per the card is temperature 1.0, top_p 0.95 and top_k 40
  7. The GGUF card's llama.cpp example path omits the quant from the file name; the real files are named like Qwen3-Coder-Next-Q4_K_M-00001-of-00004.gguf
  8. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, Kolibri-1 or Qwen3-Coder-Next?

Kolibri-1 scores 61 (C) on agent readiness against Qwen3-Coder-Next's 57.6 (C), and leads in 3 of 4 scored categories. Qwen3-Coder-Next leads on reach.

Other comparisons with Kolibri-1 or Qwen3-Coder-Next

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.