Instructions to use AtomicChat/Qwen3.8-Flash-Next-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 AtomicChat/Qwen3.8-Flash-Next-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 AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf AtomicChat/Qwen3.8-Flash-Next-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 AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf AtomicChat/Qwen3.8-Flash-Next-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 AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf AtomicChat/Qwen3.8-Flash-Next-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 AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M
Use Docker
docker model run hf.co/AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M
- LM Studio
- Jan
- vLLM
How to use AtomicChat/Qwen3.8-Flash-Next-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "AtomicChat/Qwen3.8-Flash-Next-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": "AtomicChat/Qwen3.8-Flash-Next-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Ollama
How to use AtomicChat/Qwen3.8-Flash-Next-GGUF with Ollama:
ollama run hf.co/AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Unsloth Desktop
- Pi
How to use AtomicChat/Qwen3.8-Flash-Next-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf AtomicChat/Qwen3.8-Flash-Next-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": "AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use AtomicChat/Qwen3.8-Flash-Next-GGUF with Docker Model Runner:
docker model run hf.co/AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Lemonade
How to use AtomicChat/Qwen3.8-Flash-Next-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.Qwen3.8-Flash-Next-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use AtomicChat/Qwen3.8-Flash-Next-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 AtomicChat/Qwen3.8-Flash-Next-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 AtomicChat/Qwen3.8-Flash-Next-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use AtomicChat/Qwen3.8-Flash-Next-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf AtomicChat/Qwen3.8-Flash-Next-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 "AtomicChat/Qwen3.8-Flash-Next-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"
NGram to SSD streaming?
How do you do just that? Do I ommit --no-mmap or do I just run it like any other MoE models and the NGRAM table lookup just automatically sits in the SSD?
Hi @dandandelion !
The most important flag is -fit off
I already did everything to make it work for you - just split the model into shards with a specific layout, where the ngram sits in one big shard that gets offloaded to ssd, that's it!
So yeah just download and use this flag, like in a model card
This poses potential problem with my setup. Here's how I ran the former 122B-A10B Qwen3.5
First off, my system is hybrid
16GB VRAM (RTX 3080 Ti Laptop)
64GB DDR5-4800
So already, my VRAM is constraint, so I essentially offload rest of the experts that don't fit my VRAM to system RAM using --n-cpu-moe N
./llama-server -m ./models/model-file.gguf --alias "Qwen3.5-122B-A10B" -ngl 99 -fit off --n-cpu-moe 42 -c 262144 -ctk q4_0 -ctv q4_0 --jinja --no-mmap --host 0.0.0.0 --port 8090 -fa on -b 2560 -ub 2560 --reasoning on --reasoning-preserve -np 1 --kv-tail-tokens 2048 -t 6 --temp 0.6 --top-p 0.95 --min-p 0.0 --presence-penalty 1.5 --repeat-penalty 1.0
This is the dilemma here, I have no clue how to do it with this model that has this outlying 51B N-gram. My plan was do what I was doing already and stream the 51B in SSD but even looking it up, what other people were recommending was -ot + mmap which then poses another problem cause mmap essentially puts my experts to SSD too once I even touch my tried and tested -ot or -ncmoe offloading.
@dandandelion see https://github.com/ggml-org/llama.cpp/pull/27794
and https://github.com/ggml-org/llama.cpp/pull/27837 that does some followup fixes.
just curious if directio also can work similar to mmap here
just curious if directio also can work similar to mmap here
The second pr i linked allows for that, but I dont know if it was tested, so you should.
How are you loading it?

