Vision and MTP head please!

#1
by sniper1999 - opened

Can you ship this model with Vision mmproj and MTP head as well please?
The Authors of this model has not shipped a native MTP trained on their finetune, but i think the original Qwen MTP works according to these repos who had managed to include the mtp heads as well...
https://huggingface.co/Myric/KAT-Coder-V2.5-Dev-MTP-APEX-GGUF
https://huggingface.co/gbuzhf/KAT-Coder-V2.5-Dev-MTP-GGUF

Also what might be the best quants for vision and MTP for this model?

Hi @sniper1999 !

Thanks for asking about this.

About Vision (mmproj):
Unfortunately KAT-Coder V2.5 is strictly a text and code model. The config.json has a vision_config block only because it was derived from the upstream Qwen MoE template, but looking into the actual weights there are zero visual tensors in the checkpoint. Kwaipilot didn't train a vision encoder or projector for this model, so using an external mmproj won't work with it.

About the MTP Head:
You were spot on about this one! Since KAT-Coder shares the Qwen3.6-35B-A3B architecture, the donor MTP head works great with it for speculative decoding.

I just uploaded the companion draft file to the repo:
mtp-KAT-Coder-V2.5-Dev-Q4_0.gguf

As for the best quant for MTP, Q4_0 is pretty much the sweet spot. It stays light on VRAM (around 1.1 GB) and keeps the acceptance rate high without wasting extra memory on higher bit-depths for speculative draft passes.

You can run it in llama.cpp like this:

llama-server -m KAT-Coder-V2.5-Dev.APEX-I-MiniPlus-V2.1.gguf --model-draft mtp-KAT-Coder-V2.5-Dev-Q4_0.gguf --draft-max 4 -ngl 99 -c 8192

Hope that gives you the speed boost you were looking for!

Thanks for the quick reply and adding the MTP head!
I have yet to try your quants, but they seem promising!

Anyways I did a quick search across HF and found 2 instances of vision being added to this model, but their implementation is not ideal and they fail in OCR it seems...
https://huggingface.co/jason-schulz/KAT-Coder-V2.5-Dev-VL-oQ8e-mtp
https://huggingface.co/sluttybutfast/KAT-Coder-V2.5-Dev-Vision-OptiQ-4bit

Btw which actual Qwen35B finetune do you prefer for Agentic Coding? (I did go through zephel01's blog-posts)
I was confused between Kat-coder and Occamy....seems like i would have to use both (1 for coding and another for general use plus vision)

Glad to help!

You're right about those vision ports: they frankenmerged Qwen's vision tower onto KAT-Coder without retraining the projection layer, so the visual alignment is broken and OCR fails.

As for KAT-Coder vs Occamy (and zephel01's notes), keeping both is definitely the way to go:

Occamy is your multimodal all-rounder. In zephel01's benchmarks it scored 90-93% and stayed rock-solid up to 65k context. If you need vision for UI bugs, screenshots, or broader architecture tasks, use Occamy.

KAT-Coder is a pure terminal coding specialist. It has tighter tool-calling discipline, writes very concise thinking blocks, and with the new MTP head it's much faster for raw coding, debugging, and CLI agent workflows (like Aider or Claude Code).

So basically: Occamy whenever you need vision and multi-file design, and KAT-Coder + MTP when you want maximum speed on pure terminal coding tasks.

Sign up or log in to comment