Instructions to use Hob-forge/Qwen-Drive-1.0-4B-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 Hob-forge/Qwen-Drive-1.0-4B-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 Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf Hob-forge/Qwen-Drive-1.0-4B-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 Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
Build from source code
git clone https://github.com/ggml-org/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-app # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama serve -hf Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama cli -hf Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
Use Docker
docker model run hf.co/Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
- Llama new
- LM Studio
- Jan
- vLLM
How to use Hob-forge/Qwen-Drive-1.0-4B-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Hob-forge/Qwen-Drive-1.0-4B-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": "Hob-forge/Qwen-Drive-1.0-4B-GGUF", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Describe this image in one sentence." }, { "type": "image_url", "image_url": { "url": "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg" } } ] } ] }'Use Docker
docker model run hf.co/Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
- Ollama
How to use Hob-forge/Qwen-Drive-1.0-4B-GGUF with Ollama:
ollama run hf.co/Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
- Unsloth Desktop
- Pi
How to use Hob-forge/Qwen-Drive-1.0-4B-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use Hob-forge/Qwen-Drive-1.0-4B-GGUF with Docker Model Runner:
docker model run hf.co/Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
- Lemonade
How to use Hob-forge/Qwen-Drive-1.0-4B-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.Qwen-Drive-1.0-4B-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use Hob-forge/Qwen-Drive-1.0-4B-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 Hob-forge/Qwen-Drive-1.0-4B-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 Hob-forge/Qwen-Drive-1.0-4B-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use Hob-forge/Qwen-Drive-1.0-4B-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Hob-forge/Qwen-Drive-1.0-4B-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 "Hob-forge/Qwen-Drive-1.0-4B-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"
Qwen-Drive-1.0-4B GGUF
GGUF builds of the vision-language model in Qwen/Qwen-Drive-1.0-4B (Apache-2.0), for llama.cpp and anything built on it. There are eight sizes, from 8.4 GB down to 1.9 GB, plus the vision projector.
This is an independent conversion. It is not made or endorsed by the Qwen team or the llama.cpp project.
What is and isn't in these files. Qwen-Drive is a Qwen3.5-4B vision-language model with two extra modules: a BEV perception head (3D detection, occupancy, map segmentation) and a flow-matching Planning Expert that outputs driving trajectories. Only the vision-language model is here. It chats and answers questions about images, including driving scenes. The perception head and the planner are not llama.cpp models and are not included. This is not a driving system and must never control a vehicle.
Which file should I download?
The two numbers in the right-hand columns are measured against the BF16 GGUF over ~9k held-out tokens (see "How we checked"). Lower KL means closer to the original.
Every file runs CPU-only. With a GPU, put as many layers on it as fit (-ngl), and llama.cpp keeps the rest in RAM.
| File | Size | Fits in about (estimate) | Mean KL vs BF16 | Same top token |
|---|---|---|---|---|
Qwen-Drive-1.0-4B-BF16.gguf |
8.4 GB | 10 GB | 0 (reference) | 100% |
Qwen-Drive-1.0-4B-Q8_0.gguf |
4.5 GB | 6 GB | 0.0021 | 97.3% |
Qwen-Drive-1.0-4B-Q6_K.gguf |
3.5 GB | 5 GB | 0.0136 | 94.7% |
Qwen-Drive-1.0-4B-Q5_K_M.gguf |
3.1 GB | 4.5 GB | 0.0194 | 92.8% |
Qwen-Drive-1.0-4B-Q4_K_M.gguf |
2.7 GB | 4 GB | 0.0504 | 88.9% |
Qwen-Drive-1.0-4B-IQ4_XS.gguf |
2.5 GB | 4 GB | 0.0640 | 88.0% |
Qwen-Drive-1.0-4B-Q3_K_M.gguf |
2.3 GB | 3.5 GB | 0.1781 | 80.4% |
Qwen-Drive-1.0-4B-Q2_K.gguf |
1.9 GB | 3 GB | 0.4202 | 71.4% |
mmproj-Qwen-Drive-1.0-4B-F16.gguf |
0.67 GB | (add to any of the above for images) |
Our pick:
- Q5_K_M, if you have 8 GB of RAM or more.
- Q4_K_M, on tighter machines.
- Q8_0, if you want it practically identical to the original.
Q3_K_M and Q2_K are for very small machines; expect visibly weaker answers. The "fits in about" column includes the vision projector and a modest context. Longer contexts need more.
Run it
llama.cpp (chat with images), current upstream; no patch needed:
llama-mtmd-cli -m Qwen-Drive-1.0-4B-Q5_K_M.gguf --mmproj mmproj-Qwen-Drive-1.0-4B-F16.gguf \
--image street.jpg -p "Describe this driving scene. What should the driver watch out for?"
llama.cpp server (OpenAI-compatible, text + images):
llama-server -m Qwen-Drive-1.0-4B-Q5_K_M.gguf --mmproj mmproj-Qwen-Drive-1.0-4B-F16.gguf --jinja -c 16384
LM Studio: search Hob-forge/Qwen-Drive-1.0-4B-GGUF, pick a file from the table, and keep the mmproj next to it for images.
The model thinks before answering by default (Qwen3.5 template). To turn thinking off with llama-server, pass
"chat_template_kwargs": {"enable_thinking": false} in the request.
How we made it
- The upstream checkpoint stores the VLM under a
vlm.prefix, with its config nested invlm_config. We lifted both out unchanged, giving a plainQwen3_5ForConditionalGenerationwith 723 tensors. No weights were modified. - The config lists one MTP (multi-token prediction) layer, but the weights contain none, so we converted with
--no-mtp. - We converted to BF16 with llama.cpp's
convert_hf_to_gguf.py, then quantized from that BF16.- Every quant except Q8_0 uses an importance matrix computed on the BF16 over a general calibration text (129 ร 512 tokens).
- We built the vision projector with
--mmproj, at F16.
How we checked
- Conversion vs the original. We ran the HF checkpoint in float32 on CPU over a 120-token chat and compared logits with the BF16 GGUF: top-1 agreement 119/120, mean KL 0.0002. The GGUF computes what the original computes.
- Quants vs BF16. We ran
llama-perplexity --kl-divergenceover ~9k tokens of held-out English technical text (not the calibration text). Those are the numbers in the table above. Same-top-token is the share of positions where the quant's most likely next token equals the BF16's. - Vision. We ran a smoke test on Q4_K_M + mmproj: it correctly described a forest image (tree, hanging lanterns, leaf-shaped hammock).
Not tested:
- driving-benchmark accuracy;
- long contexts;
- GPU backends other than CPU;
- non-English prompts.
Please report anything odd in the Community tab.
Licence
Apache-2.0, same as the original. All credit for the model goes to the Qwen team: see the technical report and QwenLM/Qwen-Drive-1.0.
Made by Hob-forge: verified quants of models other people can't run yet.
- Downloads last month
- 820
2-bit
3-bit
4-bit
5-bit
6-bit
8-bit
16-bit