Instructions to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with Transformers:
# Load model directly from transformers import AutoModel model = AutoModel.from_pretrained("mradermacher/KAT-Coder-V2.5-Dev-GGUF", device_map="auto") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Use Docker
docker model run hf.co/mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with Ollama:
ollama run hf.co/mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
- Unsloth Studio
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for mradermacher/KAT-Coder-V2.5-Dev-GGUF to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for mradermacher/KAT-Coder-V2.5-Dev-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for mradermacher/KAT-Coder-V2.5-Dev-GGUF to start chatting
- Pi
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @mariozechner/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Hermes Agent new
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat new
- OpenClaw new
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
- Docker Model Runner
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with Docker Model Runner:
docker model run hf.co/mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
- Lemonade
How to use mradermacher/KAT-Coder-V2.5-Dev-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull mradermacher/KAT-Coder-V2.5-Dev-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.KAT-Coder-V2.5-Dev-GGUF-Q4_K_M
List all available models
lemonade list
.mmproj files incorrect
Hi,
thank you for the quants. The multi-modal .gguf files looks incorect - only 1.4kB
Kindly asking for reupload of correct files π
Best,
Pilo
If i remember correctly we dont quant .mmproj, i think you have to use the original one
@piloponth The original KAT-Coder-V2.5-Dev is a text-only model and completely lacks the vision stack so there is no vision stack to be extracted which is the reason why the mmproj files are empty:
This repository contains the model weights and configuration files for the post-trained KAT-Coder-V2.5-Dev in the Hugging Face Transformers format. The artifacts are compatible with Hugging Face Transformers, vLLM, SGLang, KTransformers, etc. Note: this open-weight release ships only the language-model weights and operates as a text-only model; the vision/multimodal components are not included and are unavailable
If i remember correctly we dont quant .mmproj, i think you have to use the original one
We do extract mmproj and provide them in F16 and Q8_0 for models we believe are vision models but sometimes we wrongly assume a model to be a vision model if metadata and architecture indicates it to be one as we automated the determination if a model is a vision model.
Thank you gentleman for both responses.
I followed the simonko's idea and tried to pair your .gguf with .mmproj from unsloth/Qwen3.6-35B-A3B-GGUF/blob/main/mmproj-F16.gguf. And that worked. I don't know how, or if it should, but it correctly recognized supplied images and PDFs.
Thank you gentleman for both responses.
I followed the simonko's idea and tried to pair your .gguf with .mmproj from unsloth/Qwen3.6-35B-A3B-GGUF/blob/main/mmproj-F16.gguf. And that worked. I don't know how, or if it should, but it correctly recognized supplied images and PDFs.
yeah sometimes its good to frankenstein diffrent mmproj with diffrent ggufs, since some models have better vission, and some dont have vission at all
Yes you can almost always use the vision stack of the parent model for a text-only finetune of the same parent. Just keep in mind that the finetuning was done without vision in mind so the vision quality is usually a bit unpredictable depending on how the model was finetuned. LLM and vision stack are somewhat independent and so Frankenstein merge text and vision stack between closely related models technically works.