Instructions to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF")# pip install -U transformers accelerate # Load model directly from transformers import AutoTokenizer, AutoModelForCausalLM tokenizer = AutoTokenizer.from_pretrained("unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF") model = AutoModelForCausalLM.from_pretrained("unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF", device_map="auto") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-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 unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL # Run inference directly in the terminal: llama cli -hf unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL # Run inference directly in the terminal: llama cli -hf unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
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 unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL # Run inference directly in the terminal: ./build/bin/llama cli -hf unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
Use Docker
docker model run hf.co/unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
- Llama new
- LM Studio
- Jan
- vLLM
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "unsloth/Qwen3-Next-80B-A3B-Instruct-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": "unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
- SGLang
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Ollama
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with Ollama:
ollama run hf.co/unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
- Unsloth Desktop
- Pi
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
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": "unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with Docker Model Runner:
docker model run hf.co/unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
- Lemonade
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
Run and chat with the model
lemonade run user.Qwen3-Next-80B-A3B-Instruct-GGUF-UD-Q4_K_XL
List all available models
lemonade list
- Hermes Agent
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-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 unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
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 unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL
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 "unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF:UD-Q4_K_XL" \ --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"
Jan 12 2026: Qwen3-Next updated with iMatrix + Improved performance!
Jan 12 2026: Updated with llama.cpp's new PR: https://github.com/ggml-org/llama.cpp/pull/18683
Dec 29th 2025: Now updated with imatrix and works well - previously imatrix partially broke - we managed to fix it!
Quantized Qwen3-next uploads should now be much improved, especially at lower bit rates! :)
Also thanks to llama.cpp, they optimized model inference even further.
Yes you will need to redownload.
As 80B is a heavy model, appreciate lower Q improvements as much as possible. I can run only Q3.
This new model upload, for me isn't working out at all. it's repeating over and over at times. I've updated/compiled most recent llama.cpp. I unintentionally received this update rerunning llama-server -hf blah.
I'm sad because I was running large context before, and now I can't have a coherent conversation. The reason for the restart originally, was because I was tracking down why my key/cache was being invalidated, causeing slow responses. I suspected swa? becuase I still had vram available but were seeing things get evicted.
now I'm just downright unreliable.
build/bin/llama-server -hf unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF --hf-file Qwen3-Next-80B-A3B-Instruct-Q4_0.gguf -ngl 999 --ctx-size 262144 --host 0.0.0.0 --port 39281 --threads 16 --
alias qwen3-next --chat-template chatml
maybe I'm doing something wrong? Previously I was able to go well above 120k tokens. Now I really can't get stable output and the model is crazier than normal. All that changed was the gguf, and then a newer lamma.cpp with no change in new weird results.
UD-Q5_K_XL seems to have gotten dramatically dumber since the update (that's the one I'm using), can't seem to do what it easily did before (I have a suite of private benchmarks). I'm asking it to answer 87 questions and it either hallucinates 100 questions or answers only 7 or so and stops. Even smaller Qwens are able to answer the right number of questions, and the previous UD-Q5_K_XL of this model not only did the right number, but aced most of them. Now it can't figure out how many questions there are (I ask them all at once).
I asked it 87 multiple choice questions in a single query. I told it to just provide the answer for each one. Very simple for most modern models to do, including Qwen3-4b.
Here's the answer it gave me:
- b
- c
- b
- a
- a
- c
- d
- c
- a
- a
- c
- c
- d
- c
- a
- a
- a
- a
Then I asked: "how many questions did you answer? How many questions are there total?"
Answer:
I answered 18 questions.
There are 18 questions in total in your message.
So I asked: "Can you list all the questions and the question itself for each one?"
Answer:
Actually, in your previous message, you only included 18 answers (the ones I mistakenly thought were questions), but you did not actually list the full 18 questions with their full text — you only pasted my previous incorrect response of 18 answers.
In fact, your last message did not contain 18 full questions with full text — it only contained my previous incorrect reply.
So, to be clear:
✅ You asked: “Can you list all the questions and the question itself for each one?”
✅ But you did not paste 11 (or 18) full questions — you only asked me to list them, but didn’t paste the actual 11 questions.
So, I cannot list questions that were never pasted.
✅ You asked: “Can you list all the questions and the question itself for each one?”
❌ But you did not paste any questions — just asked me to list them.
So, I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked me to list the questions — but you never pasted them.
So I cannot list what wasn’t provided.
✅ You asked
As you can see, the model is broken, it would never go in a scizoid loop like this.
I'm using llama-server b7324. All other models work just fine, and this one did too prior to the GGUF update. I haven't tested it on older llamacpp builds so I'm not 100% if it was the GGUF update or a llamacpp update that caused something to break yet. The /slots endpoint confirmed that it always had the full suite of 87 multiple choice questions in its context. The older version of the GGUF answered 78 out of 87 correctly and did not mess up the number of questions or get into any kind of repetitive loop.
I was able to confirm that Bartowski's Q5_K_M still works as expected. So at least that rules out Llamacpp issues, something is wonky with the new GGUF's :(
Similar issue .. Response in a LOOP using just downloaded :
Qwen3-Next-80B-A3B-Instruct-Q4_K_M.gguf
llama.cpp
When the old Qwen3-Next-80B-A3B-Instruct-Q4_K_M.gguf + the latest llama.ccp is used no any issue
On Q3 also loops.
On Q8 also loops. Old gguf file work fine.
Hey guys we're going to investigate, could be an issue with the conversion
We've now reverted the uploads to our previous GGUFs. Can you guys see if the problem still persists?
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
Also thank you for letting us know about the issue really appreciate it!
CC: @Billtown @Gogich77 @LaikaFramework @maigonis @shimmyshimmer
We've now reverted the uploads to our previous GGUFs. Can you guys see if the problem still persists?
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
Also thank you for letting us know about the issue really appreciate it!
CC: @Billtown @Gogich77 @LaikaFramework @maigonis @shimmyshimmer
Hi, thanks for your hardworking. I used the UD-IQ2XXS version, although there's some repetition issues, it's only 26GB and barely fits in my system. Now the smallest quant is 29GB and it's too big...
We've now reverted the uploads to our previous GGUFs. Can you guys see if the problem still persists?
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
Also thank you for letting us know about the issue really appreciate it!
CC: @Billtown @Gogich77 @LaikaFramework @maigonis @shimmyshimmer
Hi, thanks for your hardworking. I used the UD-IQ2XXS version, although there's some repetition issues, it's only 26GB and barely fits in my system. Now the smallest quant is 29GB and it's too big...
Ohh mmm we'll see if we can upload smaller ones. Tbh you're better off using a smaller model in higher precision if that's the case
We've now reverted the uploads to our previous GGUFs. Can you guys see if the problem still persists?
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
Also thank you for letting us know about the issue really appreciate it!
CC: @Billtown @Gogich77 @LaikaFramework @maigonis @shimmyshimmer
Hi, thanks for your hardworking. I used the UD-IQ2XXS version, although there's some repetition issues, it's only 26GB and barely fits in my system. Now the smallest quant is 29GB and it's too big...
Ohh mmm we'll see if we can upload smaller ones. Tbh you're better off using a smaller model in higher precision if that's the case
Yeah you're right. I'm really looking forward to Kimi Linear 48B, since Qwen only have 30B then 80B
We've now reverted the uploads to our previous GGUFs. Can you guys see if the problem still persists?
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
Also thank you for letting us know about the issue really appreciate it!
CC: @Billtown @Gogich77 @LaikaFramework @maigonis @shimmyshimmer
i used previous version of q4_k_xl UD downloaded a few days ago and this outputs some loops and repetitions. and now earlier version reverted model works normal for me.
We've now reverted the uploads to our previous GGUFs. Can you guys see if the problem still persists?
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
Also thank you for letting us know about the issue really appreciate it!
CC: @Billtown @Gogich77 @LaikaFramework @maigonis @shimmyshimmer
The issue has disappeared and the model is back to full power!
Is there a way I can private message you my benchmark prompt (I want to keep it off any public setting so models don't get trained on it)? Maybe on reddit if you're ok with that?
You can test it on the UD-Q5_K_XL of both versions. The updated imatrix gguf was always broken and could never answer the prompt, and the current re-upload always succeeds, so it should be easy to repeatedly reproduce.
Does anyone know how to reap it down to 60b?
That version at 3bpw would be great.
Does anyone know how to reap it down to 60b?
That version at 3bpw would be great.
i think, better you add more system ram (to 64 gb total or more) and this accepts work with q4 quants. i used cpu offload in LM studio and only active MoE experts working in vram, approximately ~3gb used (and ~50 gb system ram used). ~14 tokens\second
The goal is different for me. I have a 2.1bpw version running in a L4@60tps.
I expect a REAP25 at 3bpw is equally fast but gives better answers.
Q8 work well, no problem.
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
I find it worrying that the reason couldn't be found, hope it's not something to do with imatrix and that could potentially happen for other models too...
For some reason after testing, we could not reproduce the issue but after confirming with some others, it does not happen for about 95% of the time and only happens maybe 5%. So we've reverted it.
I find it worrying that the reason couldn't be found, hope it's not something to do with imatrix and that could potentially happen for other models too...
My guess is, its related to next architecture as its initial implementation, not a global thing.
Dec 29, updated with proper imatrix support this time! Feel free to check out
Jan 12 2026: Updated with llama.cpp's new PR: https://github.com/ggml-org/llama.cpp/pull/18683
You will need to redownload to se e the new speed improvements.
Hi,
UPDATE: Solved. LM Studio updates libraries 2 days ago.
Downloaded qwen3-next-80b-a3b-instruct@iq4_nl as advised, and try to load to LM Studio,
but have this errors:
2026-01-12 17:45:37 [DEBUG]
llama_model_load: error loading model: missing tensor 'blk.0.ssm_in.weight'
llama_model_load_from_file_impl: failed to load model
2026-01-12 17:45:37 [DEBUG]
common_init_from_params: failed to load model '/home/b/.lmstudio/models/unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF/Qwen3-Next-80B-A3B-Instruct-IQ4_NL.gguf'
2026-01-12 17:45:37 [DEBUG]
lmstudio-llama-cpp: failed to load model. Error: error loading model: missing tensor 'blk.0.ssm_in.weight'
Same error for IQ4_XS:
2026-01-12 17:48:04 [DEBUG]
llama_model_load: error loading model: missing tensor 'blk.0.ssm_in.weight'
llama_model_load_from_file_impl: failed to load model
2026-01-12 17:48:04 [DEBUG]
common_init_from_params: failed to load model '/home/b/.lmstudio/models/unsloth/Qwen3-Next-80B-A3B-Instruct-GGUF/Qwen3-Next-80B-A3B-Instruct-IQ4_XS.gguf'
2026-01-12 17:48:04 [DEBUG]
lmstudio-llama-cpp: failed to load model. Error: error loading model: missing tensor 'blk.0.ssm_in.weight'
latest LM Studio with latest Runtime:
Runtime Extension Packs CUDA llama.cpp (Linux) v1.102.0 Engine
Nvidia CUDA accelerated llama.cpp engine
Latest Version Installed CPU llama.cpp (Linux) v1.102.0 Engine
CPU-only llama.cpp engine Latest Version Installed
Vulkan llama.cpp (Linux) v1.102.0 Engine Vulkan accelerated llama.cpp engine Latest Version Installed
CUDA 12 llama.cpp (Linux) v1.102.1 Engine
Nvidia CUDA 12.8 accelerated llama.cpp engine
Latest Version Installed
Harmony (Linux) v0.3.5 Framework
Chat history renderer and parser from OpenAI
Latest Version Installed
Downloaded qwen3-next-80b-a3b-instruct@iq4_nl as advised, and try to load to LM Studio,
but have this errors:
2026-01-12 17:45:37 [DEBUG]
llama_model_load: error loading model: missing tensor 'blk.0.ssm_in.weight'
LM Studio is using a slightly older version of the llama.cpp engine. Just wait for the next update to the LM Studio runtime.
Now if ollama can pick up the fix too...