llama.cpp now runs Aleph Alpha's Kolibri-1, and the Q4_K_M file takes 49.8 GB
llama.cpp build b11709, published on October 17, 2026, adds support for Kolibri-1, a German and English model from Aleph Alpha with 78 billion parameters. GGUF files range from 17.6 GB to 156.3 GB, so the model can run without the data-center GPUs its maker lists as the minimum. A later build adds a way to find and download models from the web interface.
llama.cpp, the open-source runtime that runs language models on ordinary computers, supports Kolibri-1 as of build b11709, published on October 17, 2026. Aleph Alpha, a German AI company, released the model on October 3, 2026, under the Apache 2.0 license. Its own instructions describe serving on data-center GPUs, while GGUF files for llama.cpp start at 17.6 GB.
What Kolibri-1 is
Kolibri-1 is a mixture-of-experts model built for German and English. It has 78 billion parameters, but only 3.46 billion are active for each token. Each of its 50 layers holds 384 experts, which are smaller subnetworks, plus one shared expert, and a router picks six experts per token.
The native context length is 262,144 tokens, and the company says it has validated quality up to 1,048,576 tokens. On the GPQA Diamond science benchmark, Aleph Alpha reports a score of 84.3 in English and 81.3 in German. These are the vendor's own measurements.
What llama.cpp added
The change converts Aleph Alpha's weights into a GGUF file and describes the model's layer layout to llama.cpp. Most attention layers look only at the preceding 512 tokens, and every fifth layer sees the whole context. According to the author, the FP8 checkpoint Aleph Alpha published needs no special handling.
How large each file is
Quantization stores weights with fewer bits per value, which makes the file smaller at some cost in accuracy. The quantizer bartowski has published GGUF files of Kolibri-1 made with build b11716. The sizes below are as Hugging Face lists them.
IQ1_Sis the smallest file, at 17.6 GB.IQ2_Mtakes 28.1 GB.Q3_K_Mtakes 37.6 GB.Q4_K_Mtakes 49.8 GB.Q6_Ktakes 69.0 GB, andQ8_0takes 83.1 GB.- The unquantized
BF16copy takes 156.3 GB.
What fits on which machine
A model runs at a usable speed only when the file, plus room for the context and the operating system, fits in memory. This suggests that a 32 GB machine can hold only the smallest variants. At 64 GB, Q4_K_M fits, while Q8_0 needs more. For the FP8 weights of about 78 GB, Aleph Alpha lists two 80 GB A100 cards or one H200 as the minimum.
The author of the change measured 106.01 tokens per second of generation with their own Q4_K_M build, on a server with four A800 cards. No measurement on a home computer has been published, and no independent quality test of the quantized files exists yet.
Finding models from the web interface
Build b11714, published the same day, adds a Discover Models view to the web interface of llama-server. It searches GGUF models on Hugging Face, shows whether each variant fits in memory, and downloads it with pause and resume. The setting is off by default and has to be enabled in the interface.
Sources
Related
llama.cpp now runs Reflection's Beam, and its smallest GGUF file is 103.1 GB
llama.cpp build b11701 adds support for Beam, Reflection's open model with 501 billion parameters, released on October 16, 2026. Unsloth has published GGUF files ranging from 103.1 GB to about 1 TB, so the model can now run outside server stacks such as vLLM and SGLang. No speed measurement has been published yet.
llama.cppverified
llama.cpp now runs PrismML's ternary Bonsai 2 27B without the company's fork
Build b11556 adds the weight rotation step that Bonsai 2 27B was missing in stock llama.cpp. The 7.63 GB Q2_0 file now gives correct output there, while PrismML's smaller PQ2_0 and PTQ1_0 packs still require the company's own build.
llama.cppverified

Google open-sources ML Drift, the GPU engine inside LiteRT, and stops adding features to the TFLite GPU delegate
Google's AI Edge team released ML Drift under the Apache 2.0 license on October 8, 2026. It is the engine that runs on-device models on the GPU in LiteRT, and it also ships as a standalone library. The older TFLite GPU delegate gets no new features from now on, so apps built on it face a migration.
Google Developers Blogverified