KAT Coder V2.5 Dev APEX I MiniPlus V2.1 needs about 2.4 GB of memory at Q4_0 (a 1.2 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 2 quants, from 1.2 GB (Q4_0) to 14.8 GB. Longer context needs more: at 32K tokens the KV cache alone adds about 2.8 GB.
KAT Coder V2.5 Dev APEX I MiniPlus V2.1 – 34.7B parameter Qwen3.5 MOE model
KAT Coder V2.5 Dev APEX I MiniPlus V2.1 is a 34.7B parameter Qwen3.5 MOE model. It is trained for coding and reasoning tasks. The model is released under the apache-2.0 license and is text‑only, with no vision support.
Good at
- Coding tasks
- Reasoning
- Agentic coding
Limits
- No vision or multimodal support
- Requires 8k context for memory estimates
- Large VRAM needed for full precision
Best for
- Code generation
- Debugging assistance
- Automated coding agents
Who it’s for. Developers and researchers needing a large‑scale coding model with MOE architecture. The model is suitable for users with sufficient GPU memory to run the Q4_0 quantized version or larger variants.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_0 | 1.2 GB | 2.4 GB | Fits | Get file → | |
| — | 14.8 GB | 15.9 GB | Too big | Get file → |
For 8 GB VRAM, use the Q4_0 quantized file (1.19 GB, ~2.4 GB memory at 8k context). If you have 16 GB VRAM, the full precision file (14.75 GB, ~15.9 GB memory at 8k context) is available. Memory estimates are approximate.
What GPU do you need for KAT Coder V2.5 Dev APEX I MiniPlus V2.1?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is Q4_0 (1.2 GB file, about 2.4 GB in use).
- 6 GB VRAM: the best quant that fits is Q4_0 (1.2 GB file, about 2.4 GB in use).
- 8 GB VRAM: the best quant that fits is Q4_0 (1.2 GB file, about 2.4 GB in use).
- 12 GB VRAM: the best quant that fits is Q4_0 (1.2 GB file, about 2.4 GB in use).
- 16 GB VRAM: the best quant that fits is the main file (14.8 GB file, about 15.9 GB in use).
Which KAT Coder V2.5 Dev APEX I MiniPlus V2.1 quant should you choose?
Q4_0 (1.2 GB) is the middle option in this repository. The usual sweet spot between file size and quality, and the quant most people start with.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about KAT Coder V2.5 Dev APEX I MiniPlus V2.1
How much VRAM does KAT Coder V2.5 Dev APEX I MiniPlus V2.1 need?
About 2.4 GB at Q4_0 with an 8K context window. That is the 1.2 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run KAT Coder V2.5 Dev APEX I MiniPlus V2.1 on an 8 GB GPU?
Yes, with Q4_0: the 1.2 GB file needs about 2.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of KAT Coder V2.5 Dev APEX I MiniPlus V2.1 GGUF?
It depends on the quant: Q4_0 is 1.2 GB, file is 14.8 GB.
What context length does KAT Coder V2.5 Dev APEX I MiniPlus V2.1 support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.7 GB at 8K and 2.8 GB at 32K.
Where can I download KAT Coder V2.5 Dev APEX I MiniPlus V2.1 GGUF?
The files are on Hugging Face in the IsValorum/KAT-Coder-V2.5-Dev-APEX-I-MiniPlus-V2.1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does KAT Coder V2.5 Dev APEX I MiniPlus V2.1 use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
Yes, by using the Q4_0 quantized file which is 1.19 GB and requires about 2.4 GB of VRAM at 8k context.
Does this model support image inputs?
No, the model is text‑only and does not include vision or multimodal components.
What license applies to this model?
The model is released under the apache-2.0 license.