Instructions to use AesSedai/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 AesSedai/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 AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf AesSedai/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 AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf AesSedai/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 AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf AesSedai/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 AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M
Use Docker
docker model run hf.co/AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use AesSedai/Qwen3.8-Flash-Next-GGUF with Ollama:
ollama run hf.co/AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Unsloth Desktop
- Pi
How to use AesSedai/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 AesSedai/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": "AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use AesSedai/Qwen3.8-Flash-Next-GGUF with Docker Model Runner:
docker model run hf.co/AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Lemonade
How to use AesSedai/Qwen3.8-Flash-Next-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull AesSedai/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 AesSedai/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 AesSedai/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 AesSedai/Qwen3.8-Flash-Next-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use AesSedai/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 AesSedai/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 "AesSedai/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"
Keep ngram tensors unquantized
Have you done any tests to see what happens to the quality (PPL / KL divergence) when the ngram tensors remain unquantized? The size of those tensors really don't matter if they are offloaded to an SSD as the latency is identical in both cases. Might bring about some additional quality gains for "free" (other than some storage).
There's some prompt processing penalty though. I've done some exploration in this area: https://github.com/ggml-org/llama.cpp/discussions/27864
I ran several tests with IQ4_NL quantized PLE, and it seems fine with the llama.cpp correctness fixes here. Here's a report here: https://github.com/ggml-org/llama.cpp/discussions/27965
Q8_0 for the larger quants is really close in accuracy to the BF16, I was going to try some tests on Q4_K quanting the PLE tensors this weekend actually. I think that it should still show up in PPL/KLD.
IIRC, neither the DOWN tensors nor the PLE could use K quants (they weren't multiple of 256). Had to choose between iq4_nl, q4_0, q5_0, q5_1 or q8_0. @aessedai did you check the quantization logs? it is possible that all down/ple were upcasted to q8_0 already
Just checked through the metadata viewer and the PLEs for all of my quants are Q8_0 lol.
I'm interested in seeing how much the perplexity/kld gets worse if you drop the PLE to IQ4_NL
Just checked through the metadata viewer and the PLEs for all of my quants are Q8_0 lol.
So is ffn down
Q8_0 for the larger quants is really close in accuracy to the BF16, I was going to try some tests on Q4_K quanting the PLE tensors this weekend actually. I think that it should still show up in PPL/KLD.
Did you happen to run these experiments? Really curious to hear your results! They could also tell us if it could potentially be worth using bf16 for the ngram tensors.
Just checked through the metadata viewer and the PLEs for all of my quants are Q8_0 lol.
So is ffn down
I'm not yet knowledgeable enough to know if this is a good or a bad thing, re the ffn down being at Q8_0, could someone enlighten?
Just checked through the metadata viewer and the PLEs for all of my quants are Q8_0 lol.
So is ffn down
I'm not yet knowledgeable enough to know if this is a good or a bad thing, re the ffn down being at Q8_0, could someone enlighten?
If it still fits in your (v)ram it can be a good thing, as quality will be higher. But these were meant to be in Q6_K which is a smaller quant (so file size would be smaller).
If it still fits in your (v)ram it can be a good thing, as quality will be higher. But these were meant to be in Q6_K which is a smaller quant (so file size would be smaller).
OK that makes sense, I read that they were accidentally 'upscaled' and I figured that means they are at the higher quant than originally intended, but wasn't sure if that could have some adverse affect. Thanks for the info.
If it still fits in your (v)ram it can be a good thing, as quality will be higher. But these were meant to be in Q6_K which is a smaller quant (so file size would be smaller).
OK that makes sense, I read that they were accidentally 'upscaled' and I figured that means they are at the higher quant than originally intended, but wasn't sure if that could have some adverse affect. Thanks for the info.
They weren't upscaled, as that implies they were smaller to begin with. They were simply quantized less than intended, as the K quants are not compatible with the tensor shape of these particular tensor (no multiple of 256 in its dimension).
OK that makes sense, I read that they were accidentally 'upscaled' and I figured that means they are at the higher quant than originally intended, but wasn't sure if that could have some adverse affect. Thanks for the info.
They weren't upscaled, as that implies they were smaller to begin with. They were simply quantized less than intended, as the K quants are not compatible with the tensor shape of these particular tensor (no multiple of 256 in its dimension).
Right, that makes much more sense, I don't know where I got the impression of upscaling from, I am probably mixing up something I read elsewhere obviously. Thanks for taking the time to explain.