Instructions to use DogukanUrker/BTL-4-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf DogukanUrker/BTL-4-GGUF:Q4_K_M
Use Docker
docker model run hf.co/DogukanUrker/BTL-4-GGUF:Q4_K_M
- LM Studio
- Jan
- vLLM
How to use DogukanUrker/BTL-4-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "DogukanUrker/BTL-4-GGUF" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "DogukanUrker/BTL-4-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/DogukanUrker/BTL-4-GGUF:Q4_K_M
- Ollama
How to use DogukanUrker/BTL-4-GGUF with Ollama:
ollama run hf.co/DogukanUrker/BTL-4-GGUF:Q4_K_M
- Unsloth Studio
How to use DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for DogukanUrker/BTL-4-GGUF to start chatting
- Pi
How to use DogukanUrker/BTL-4-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf DogukanUrker/BTL-4-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": "DogukanUrker/BTL-4-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use DogukanUrker/BTL-4-GGUF with Docker Model Runner:
docker model run hf.co/DogukanUrker/BTL-4-GGUF:Q4_K_M
- Lemonade
How to use DogukanUrker/BTL-4-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull DogukanUrker/BTL-4-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.BTL-4-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-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 DogukanUrker/BTL-4-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use DogukanUrker/BTL-4-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf DogukanUrker/BTL-4-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 "DogukanUrker/BTL-4-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"
BTL-4 — Q4_K_M GGUF
Q4_K_M quantization of badtheorylabs/BTL-4,
a 35B-A3B MoE fine-tuned from deepreinforce-ai/Ornith-1.0-35B.
Upstream ships only IQ2_XXS (2.30 bpw). This is the 4-bit build, quantized and
measured on a 12 GB consumer GPU.
| file | size | bpw |
|---|---|---|
BTL-4-Q4_K_M.gguf |
20.1 GiB (21.5 GB) | 4.97 |
token_embd and output are held at q8_0; everything else follows the stock
Q4_K_M mixture. 733 tensors, converted from the bf16 source.
Measured on my hardware
RTX 3060 12 GB · Ryzen 5 5600 · 16 GB DDR4 · Debian · llama.cpp CUDA
| decode | 52.1 tok/s |
| prefill | 816-896 tok/s |
| load time | ~46 s (--load-mode none) |
| context | 170,000 with q8_0 KV |
Decode was sampled 12 times across an 1,837-token generation: every sample fell between 52.0 and 52.4 tok/s. Throughput at 8K context was 52.4 tok/s, so the 170K window costs about 0.7%.
Only 10 of 40 layers hold a growing KV cache and those use 2 KV heads, which is
why 170K fits at all — roughly 10 KB/token at q8_0.
Run it
llama-server -m BTL-4-Q4_K_M.gguf \
-ngl 99 --n-cpu-moe 24 -c 170000 -fa on --jinja -np 1 \
--cache-type-k q8_0 --cache-type-v q8_0 \
-b 2048 -ub 1024 \
--temp 0.6 --top-p 0.95 --top-k 20 --min-p 0.0 \
--presence-penalty 0.0 --repeat-penalty 1.0 \
--reasoning-format deepseek
This is the config I actually run, not a tuned demo. Two notes:
--reasoning-format deepseekis not optional. Without it, thinking lands incontentand accumulates every turn, and long agent runs degrade. Verified: with the flag,reasoning_contentandcontentseparate cleanly.--temp 0.6is my daily setting. Upstream published temp 1.0 / top_p 0.95 and took all of its benchmark numbers with those. Use 1.0 if you are trying to reproduce them.
Lower --n-cpu-moe if you have more VRAM, raise it toward 26–28 if you OOM.
On 16 GB of RAM, run --load-mode none and expect the load to take ~46 s;
the experts are ~93% of the weights and you do not want them paging off a
SATA disk.
Requires a llama.cpp build with qwen3_5_moe support.
What I verified
- Loads and generates correct code
- Tool calling works —
finish_reason: tool_calls, correct function and arguments, through the model's XML template with--jinja - Reasoning separation works with
--reasoning-format deepseek - It is extremely verbose. An LRU cache class took 1,837 tokens for ~400
tokens of code. Reversing a linked list took 3,744 characters of reasoning for
315 characters of answer. At
max_tokens: 400it never finished thinking and returned empty content. Budget 2–4K minimum, more for hard problems.
What is missing
No MTP. The upstream config declares mtp_num_hidden_layers: 1 and the
converter writes block_count = 41, but the checkpoint contains no mtp.* or
layers.40.* tensors — I checked the safetensors index directly, both counts are
zero. A stock loader then fails on blk.40.attn_norm.weight. This build was
converted with --no-mtp. Do not pass --spec-type draft-mtp.
No vision. The upstream checkpoint has 333 vision tensors and a
vision_config, but convert_hf_to_gguf.py drops them. This is a text-only
build with no mmproj.
On the upstream benchmark claims
I have not verified them, and this card does not repeat them as facts.
Of the three headline numbers, only BFCL v4 (AST) has a published paired
baseline: 69.2 → 73.5 on the base model, same harness, same decoding. SWE-bench
Verified (78.4%) and LiveCodeBench v6 (66.1%) are reported with — for the
base model, so the fine-tune's contribution to either is unmeasured.
Separately, upstream's IQ2_XXS build reports 94.1% behavioural retention
measured on 118 short-form factual, grounded-extraction and false-premise items.
That gate contains no coding and no tool-calling, which is what the model is for.
I plan to run both builds through the same coding and tool-use harness. Until then, treat every number above the horizontal rule as mine and everything in this section as unverified.
Quantization
Converted from badtheorylabs/BTL-4 bf16 with convert_hf_to_gguf.py --no-mtp,
then llama-quantize --token-embedding-type q8_0 --output-tensor-type q8_0.
No importance matrix. Everything ran in
ghcr.io/ggml-org/llama.cpp:full on the box described above.
License
Apache-2.0, inherited from badtheorylabs/BTL-4. The original base model,
deepreinforce-ai/Ornith-1.0-35B, is MIT.
- Downloads last month
- 460
4-bit
Model tree for DogukanUrker/BTL-4-GGUF
Base model
badtheorylabs/BTL-4