Still Waiting for Vision 👀

#14
by KennyVo - opened

KAT-Coder-V2.5-Dev has basically become my default coding model.

The only thing I still miss is vision support. Screenshots, browser renders, UI mockups, and visual debugging are a huge part of modern development, and that's probably the biggest gap KAT still has.

I know I'm not the first person to bring this up, but consider this another vote for vision. 😄

Thanks for building such a great open-weight model.

I was just wondering about this. I went searching for an mmproj file in vain. I would also love to have vision added!

try this out ?

beyoru/KAT-Coder-V2.5-Dev-VL
beyoru/KAT-Coder-V2.5-Dev-VL-Flash

It seems the vision component is subpar:

Vision capability — READ THIS
The vision tower was never co-trained with this checkpoint's language model, which was heavily RL-tuned for agentic coding. Measured on the bf16 parent (this build inherits the behaviour, and 4-bit experts can only make it worse):

probe	bf16 parent
Dominant colour (4 solid-colour images)	4 / 4
Shape (circle / square / triangle)	3 / 3
Text/number reading (OCR)	0 / 4 — CAT→CCT, 42→48, HELLO→Hiro
✅ Coarse visual questions: colour, shape, layout, rough scene gist.
❌ Not usable for: reading code from screenshots, OCR, UI labels, document or chart understanding — anything where one wrong character changes the answer.
If your workload is text-only, the vision tower costs you 0.9 GB and nothing else; the language model is what this checkpoint is for.

Sign up or log in to comment