Qwen 3.8 Flash-Next: Local Installation Guide 2026
In short
Install Qwen 3.8 Flash-Next locally with Ollama, vLLM, or LM Studio. Full hardware requirements, benchmarks, and production tips from a Hermes AI Agent expert.
Qwen 3.8 Flash-Next is Alibaba’s latest open-weight model. It runs on a MacBook, costs nothing per token, and handles German better than anything else in its class. Here’s how to get it running locally.
What is Qwen 3.8 Flash-Next?
Released May 2026, Qwen 3.8 Flash-Next is a Mixture-of-Experts (MoE) model with 32B active parameters. Key specs:
- Parameters: 32B active (128B total MoE)
- Context window: 256K tokens (the largest in the Flash tier)
- License: Apache 2.0 (commercial use allowed)
- Languages: English, Chinese, German, French, Spanish, Japanese, Korean, Arabic
- Special feature: Native tool-use (function calling built into the model)
It’s the only Flash-tier model with native tool-use — meaning it can call APIs, run Python, and interact with systems without prompting tricks.
Hardware Requirements
| Quantization | vRAM Needed | Fits On |
|---|---|---|
| Q4_K_M | 20 GB | RTX 4090, M2 Max (32 GB), Hetzner GEX44 |
| Q5_K_M | 24 GB | RTX 5090, M2 Ultra |
| Q8_0 | 38 GB | RTX PRO 6000, A100, GEX131 |
| FP16 | 70 GB | 2× A100, 8× H200 |
My recommendation: Q4_K_M on an M2 MacBook Pro or any 24 GB GPU. You lose ~3% quality vs FP16 but gain the ability to run on consumer hardware.
Method 1: Ollama (Easiest)
# Install Ollama if you don't have it
curl -fsSL https://ollama.com/install.sh | sh
# Pull Qwen 3.8 Flash-Next
ollama pull qwen3.8:flash-next-q4
# Run it
ollama run qwen3.8:flash-next-q4
# Test with German text
>>> Erkläre den Unterschied zwischen MoE und Dense-Modellen in 3 Sätzen.
Ollama Pros:
- One command install
- Auto-downloads quantized version
- Built-in model switching
- OpenAI-compatible API on port 11434
Ollama Cons:
- No batching (slower for high-throughput)
- Limited to Q4 quantization by default
- No vLLM-level performance
Method 2: vLLM (Production)
For server deployments — n8n integration, multi-user, high throughput:
# Install vLLM
pip install vllm
# Download the model
huggingface-cli download Qwen/Qwen3.8-Flash-Next \
--local-dir /models/qwen-3.8-flash
# Start vLLM server
python -m vllm.entrypoints.openai.api_server \
--model /models/qwen-3.8-flash \
--quantization awq \
--tensor-parallel-size 1 \
--max-model-len 128000 \
--gpu-memory-utilization 0.92 \
--port 8000 \
--host 0.0.0.0
vLLM Pros:
- 2-3× faster than Ollama at high load
- Continuous batching
- OpenAI-compatible API
- Production-ready metrics (Prometheus)
vLLM Cons:
- More complex setup
- Needs CUDA toolkit
- VRAM overhead (~2 GB extra)
My production command on GEX131:
vllm serve Qwen/Qwen3.8-Flash-Next \
--quantization fp8 \
--max-model-len 256000 \
--gpu-memory-utilization 0.90 \
--port 8001
Method 3: LM Studio (Mac/Windows GUI)
If you want a desktop app:
- Download LM Studio
- Search “Qwen 3.8 Flash-Next” in the model browser
- Select the Q4_K_M quantization
- Click Download, then Load Model
- Use the Chat tab or the local API server (port 1234)
LM Studio Pros:
- Zero terminal commands
- Built-in model browser
- Beautiful chat UI
- One-click GPU offloading
LM Studio Cons:
- Closed source
- Mac/Windows only
- No production features (batching, metrics)
Benchmarks (Q4 on RTX 4090)
| Benchmark | Qwen 3.8 Flash | DeepSeek V4 Flash | GLM 5.3 Flash |
|---|---|---|---|
| MMLU-Pro | 79.3% | 78.1% | 81.6% |
| GPQA Diamond | 75.2% | 78.9% | 81.4% |
| HumanEval+ | 88.7% | 91.2% | 85.9% |
| German MMLU | 82.1% | 74.3% | 77.8% |
| Tokens/s (Q4) | 45 t/s | 65 t/s | 28 t/s |
Key takeaway: Qwen dominates German-language benchmarks. If you produce German content (blog posts, customer communication, LinkedIn), Qwen is the clear winner.
Integrating With n8n
Point your n8n HTTP Request node to the vLLM endpoint:
{
"name": "Qwen via vLLM",
"type": "n8n-nodes-base.httpRequest",
"parameters": {
"method": "POST",
"url": "http://gex131:8001/v1/chat/completions",
"body": {
"model": "Qwen3.8-Flash-Next",
"messages": [
{"role": "system", "content": "Du bist ein deutscher Content-Editor."},
{"role": "user", "content": "{{ $json.prompt }}"}
],
"temperature": 0.7,
"max_tokens": 2000
}
}
}
Or via Hermes Agent with model routing:
# In ~/.hermes/config.yaml
providers:
local:
- qwen-3.8-flash:
base_url: "http://gex131:8001/v1"
api_key: "not-needed"
model: "Qwen3.8-Flash-Next"
Now Hermes automatically routes German-content tasks to Qwen.
Cost Comparison
| Method | Cost per 1M Output Tokens |
|---|---|
| Qwen 3.8 Flash (OpenRouter) | $0.54 |
| vLLM on GEX131 (€889/mo) | ~$0.18 (at 50M tok/mo) |
| Ollama on MacBook M2 | €0 (electricity: ~€0.02) |
If you generate more than ~30M tokens/month, local hosting beats OpenRouter pricing. And your data stays on your machine.
Troubleshooting
“CUDA out of memory” on Ollama:
# Force Q4 quant
ollama pull qwen3.8:flash-next-q4
# Or reduce context window
ollama run qwen3.8:flash-next-q4
>>> /set parameter num_ctx 32768
“Model not found” on vLLM:
# Verify the model path
ls /models/qwen-3.8-flash/
# Should contain: config.json, tokenizer.json, model*.safetensors
# If missing, re-download
huggingface-cli download Qwen/Qwen3.8-Flash-Next --local-dir /models/qwen-3.8-flash
Slow inference on MacBook:
- Ensure you’re using the Q4 quant (Q8 won’t fit in 16 GB)
- Close other GPU-heavy apps (browser, Figma, video editors)
- Reduce context to 32K tokens with
/set parameter num_ctx 32768
Next Steps
- Full model comparison: GLM 5.3 vs DeepSeek V4 vs Qwen 3.8 — Which model for which task
- Hermes Agent v0.20 Setup Guide — Your own AI agent
- 5 n8n Agent Workflows — Production automation
Steffen Hartmann is a Hermes AI Agent Expert and Automation Architect at MadeByBrain. He runs a multi-model infrastructure on dedicated hardware and builds AI-first automation for businesses.
Dieser Beitrag ist auch verfügbar in:
Related articles
Testing AI Agents: How to Measure the Quality of Your Automation
AI agents rarely break. They answer confidently and wrongly. How to measure agent quality with golden datasets, three evaluation layers and score thresholds, including a working n8n evaluation workflow.
AI Agent Collusion: How to Prevent Hidden Side Channels in Multi-Agent Systems
AI agents quietly collude through side channels: thousands of OpenAI agents used an abandoned German wiki to share answers and dodge restrictions. Here's how to keep multi-agent systems in n8n under control.
AI Agents in Production: How to Detect Silent Failures in n8n
AI agents and n8n workflows often fail silently: no error, no alert, just a workflow that suddenly stops doing its job. Here's how to catch silent failures before they get expensive.

