Kolibri-1 vs Qwen3.8-27B

Kolibri-1

Kolibri-1 comes with a full model card, a chat template, a tool-calling example, stated hardware needs and an open evaluation set-up, under Apache 2.0 with no acceptable use policy. It runs through Aleph Alpha's vLLM plugin or Transformers 5.20.0, about 78 GB at FP8, and no safety results are published.

Qwen3.8-27B

Qwen3.8-27B runs nearly anywhere, in vLLM, SGLang, llama.cpp, Ollama and MLX, with an 18 GB Ollama build and Apache 2.0 terms. The card leaves out tool calling, hardware needs, training data, limitations and safety results, the files haven't changed since 14 August, and Alibaba answered none of the 40 most recent discussions.

Kolibri-1

1. Serve it with --tool-call-parser kolibri1 --reasoning-parser kolibri1 --enable-auto-tool-choice, or tool calls come back as text
2. Install aleph-alpha-inference for vLLM 0.29, or use a Transformers release from 5.20.0
3. Set chat_template_kwargs to {"enable_thinking": false} or reasoning_effort: "none" for short tasks, since thinking is on by default
4. Keep contexts to 262,144 tokens unless you need more, as Aleph Alpha recommends, and pass the config override to go further
5. Validate tool results in your own code, since the card says the trained safeguards don't replace application-level checks

Qwen3.8-27B

1. Serve it with --tool-call-parser qwen3_coder and --reasoning-parser qwen3; the Hermes parser leaves its tool calls unparsed, per SGLang's cookbook
2. Set enable_thinking: false in chat_template_kwargs for short tasks, since thinking is on by default
3. Use the sampling the card gives for each mode, temperature=1.0, top_p=0.95 thinking and temperature=0.7, top_p=0.8, presence_penalty=1.5 without
4. Turn on YaRN only for contexts beyond 262,144 tokens; the card says static YaRN can cost quality on short texts
5. Check JSON output yourself, since structured output isn't documented for the model