Instructions to use AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-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/Ling-3.0-flash-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
Use Docker
docker model run hf.co/AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
- LM Studio
- Jan
- vLLM
How to use AtomicChat/Ling-3.0-flash-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
- Ollama
How to use AtomicChat/Ling-3.0-flash-GGUF with Ollama:
ollama run hf.co/AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
- Unsloth Studio
How to use AtomicChat/Ling-3.0-flash-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 AtomicChat/Ling-3.0-flash-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 AtomicChat/Ling-3.0-flash-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for AtomicChat/Ling-3.0-flash-GGUF to start chatting
- Pi
How to use AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-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": "AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- OpenClaw new
How to use AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-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/Ling-3.0-flash-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"
- Docker Model Runner
How to use AtomicChat/Ling-3.0-flash-GGUF with Docker Model Runner:
docker model run hf.co/AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
- Lemonade
How to use AtomicChat/Ling-3.0-flash-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull AtomicChat/Ling-3.0-flash-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.Ling-3.0-flash-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use AtomicChat/Ling-3.0-flash-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/Ling-3.0-flash-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/Ling-3.0-flash-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
"Tokenizer config may be incorrect" - also, unused tensors?
0.04.535.876 W load: special_eos_id is not in special_eog_ids - the tokenizer config may be incorrect
0.04.596.684 W model has unused tensor blk.41.attn_norm.weight (size = 10240 bytes) -- ignoring
0.04.596.688 W model has unused tensor blk.41.attn_q.weight (size = 16711680 bytes) -- ignoring
0.04.596.691 W model has unused tensor blk.41.attn_kv_a_mqa.weight (size = 1566720 bytes) -- ignoring
0.04.596.693 W model has unused tensor blk.41.attn_kv_a_norm.weight (size = 2048 bytes) -- ignoring
0.04.596.696 W model has unused tensor blk.41.attn_k_b.weight (size = 2228224 bytes) -- ignoring
0.04.596.698 W model has unused tensor blk.41.attn_v_b.weight (size = 2228224 bytes) -- ignoring
0.04.596.700 W model has unused tensor blk.41.attn_gate.weight (size = 87040 bytes) -- ignoring
0.04.596.703 W model has unused tensor blk.41.attn_output.weight (size = 11141120 bytes) -- ignoring
0.04.596.705 W model has unused tensor blk.41.ffn_norm.weight (size = 10240 bytes) -- ignoring
0.04.596.708 W model has unused tensor blk.41.ffn_gate_inp.weight (size = 5242880 bytes) -- ignoring
0.04.596.710 W model has unused tensor blk.41.exp_probs_b.bias (size = 2048 bytes) -- ignoring
0.04.596.712 W model has unused tensor blk.41.ffn_gate_exps.weight (size = 432537600 bytes) -- ignoring
0.04.596.715 W model has unused tensor blk.41.ffn_up_exps.weight (size = 432537600 bytes) -- ignoring
0.04.596.717 W model has unused tensor blk.41.ffn_down_exps.weight (size = 534773760 bytes) -- ignoring
0.04.596.719 W model has unused tensor blk.41.ffn_gate_shexp.weight (size = 2088960 bytes) -- ignoring
0.04.596.722 W model has unused tensor blk.41.ffn_up_shexp.weight (size = 2088960 bytes) -- ignoring
0.04.596.724 W model has unused tensor blk.41.ffn_down_shexp.weight (size = 2088960 bytes) -- ignoring
Llama.cpp outputs the above, I'm curious if it's something I forgot to do or change? I'm running with llama-server -m Ling-3.0-flash-AD-IQ3_XXS-00001-of-00002.gguf -ngl -1 -c 60000 -np 1 -ctk q8_0 -ctv q8_0 --chat-template-file ling-3.0-flash-chat-template.jinja --load-mode none --reasoning-preserve
and it has issues like writing some_file instead of some-file and sometimes puts in chinese characters. Ideas?
Edit: I should add that im using llama.cpp-pr26608
Hi @je0923 !
The problem is entirely on llama.cpp-pr26608's side.
I've recently fixed a bunch of bugs in our llama.cpp turboquant fork and currently doing a release into master, so I'd highly suggest you using it:
https://github.com/AtomicBot-ai/atomic-llama-cpp-turboquant
Please build it yourself for now using cmake. I'm going to publish a release, but it's going to take ~2 hours from now. Sorry(
Also i'm updating quants right now to fix a recently found bug, stay tuned!
Here I checked again IQ2_XS quant quickly for you to see if it's ok:
As you can see, we have exactly 42 layers, so our build runs all layers. Your PR build substracts one from the other and lands on 41.
Ling 3.0 flash has 43 layers - 42 + MTP, which I currently don't support.
Also, I suggest dropping -ctk q8_0 -ctv q8_0. On MLA the cache holds an already low-rank compressed latent, and quantizing that is a lot more lossy than quantizing a normal KV cache. We haven't validated it on this architecture.
Edit: Wait, did you update the quants themselves? Do I have to redownload? I haven't yet, if so ignore the below haha
Edit 2: Oh, I see someone mentioned the same bug! Cool, I'll wait for that fix then :D Thanks so much!
https://github.com/ggml-org/llama.cpp/pull/26608#issuecomment-5207876317
Hmm, the tensor thing is fixed - there's no warnings about that - but I may be doing something wrong with the tokenizer. I still get 0.04.520.263 W load: special_eos_id is not in special_eog_ids - the tokenizer config may be incorrect
I'm using the chat template at https://huggingface.co/inclusionAI/Ling-3.0-flash/raw/main/chat_template.jinja
When I run the model and use it with pi, it ends up doing tool calls and literally putting the arguments within the name of the file:
The user wants me to create a new file with the alphabet. Simple enough. I'll create a file containing the alphabet (a-z).
write ~/Desktop/model_runner/alphabet.txt</arg_value><arg_key>content</arg_key>
<arg_value>abcdefghijklmnopqrstuvwxyz
I feel like there's probably a super simple fix haha. I'm in pi with the llama cpp built from the link you gave and i use normal kv cache. Any ideas? It's OK if this is just a me thing, but I was just curious 😃
About a tool call corruption - isn't not the quants, reproduced it on bloomer010's files too. It's llama.cpp tool call parsers fault. It infers arg_value terminator from a sample render, picks up \n and the model doesn't emit that newline between arguments
This fix has to be in the parser. And also - single-argument tools parse fine 😄
