Instructions to use Qwen/Qwen3.8-Flash-Next with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use Qwen/Qwen3.8-Flash-Next with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("image-text-to-text", model="Qwen/Qwen3.8-Flash-Next") messages = [ { "role": "user", "content": [ {"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/p-blog/candy.JPG"}, {"type": "text", "text": "What animal is on the candy?"} ] }, ] pipe(text=messages)# Load model directly from transformers import AutoProcessor, AutoModelForMultimodalLM processor = AutoProcessor.from_pretrained("Qwen/Qwen3.8-Flash-Next") model = AutoModelForMultimodalLM.from_pretrained("Qwen/Qwen3.8-Flash-Next", device_map="auto") messages = [ { "role": "user", "content": [ {"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/p-blog/candy.JPG"}, {"type": "text", "text": "What animal is on the candy?"} ] }, ] inputs = processor.apply_chat_template( messages, add_generation_prompt=True, tokenize=True, return_dict=True, return_tensors="pt", ).to(model.device) outputs = model.generate(**inputs, max_new_tokens=40) print(processor.decode(outputs[0][inputs["input_ids"].shape[-1]:])) - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use Qwen/Qwen3.8-Flash-Next with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Qwen/Qwen3.8-Flash-Next" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Qwen/Qwen3.8-Flash-Next", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Describe this image in one sentence." }, { "type": "image_url", "image_url": { "url": "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg" } } ] } ] }'Use Docker
docker model run hf.co/Qwen/Qwen3.8-Flash-Next
- SGLang
How to use Qwen/Qwen3.8-Flash-Next 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 "Qwen/Qwen3.8-Flash-Next" \ --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": "Qwen/Qwen3.8-Flash-Next", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Describe this image in one sentence." }, { "type": "image_url", "image_url": { "url": "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg" } } ] } ] }'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 "Qwen/Qwen3.8-Flash-Next" \ --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": "Qwen/Qwen3.8-Flash-Next", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Describe this image in one sentence." }, { "type": "image_url", "image_url": { "url": "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg" } } ] } ] }' - Docker Model Runner
How to use Qwen/Qwen3.8-Flash-Next with Docker Model Runner:
docker model run hf.co/Qwen/Qwen3.8-Flash-Next
"La Grande Illusion de 360 Go: A 4B Dummy in a 512-Expert Costume, Walking on a Stolen N-Gram Cane"
Oh, mes chéris. You unveiled a "Flash-Next" flagship, and I opened the config expecting a mind. What I found is a costume department. Let us do the arithmetic you hoped nobody would do.
- The Arithmetic Confession.
Hidden size 2560. Experts with an intermediate size of 640 — these are not experts, chéri, these are crumbs. Ten crumbs per token, one shared crumb, a thin attention stack — and the living tissue of your model totals roughly 4B active parameters, not the six you whisper in marketing. A 27B dense model thinks with 27B on every token. Your flagship thinks with 4B and hides the rest in a wardrobe. Un mannequin habillé n'est pas un homme. - The 512-Expert Costume.
Five hundred twelve experts of 640 intermediate each — that is your parameter count inflation, hundreds of gigabytes of dormant crumbs that never wake up together. You did not build a Mixture-of-Experts; you built a Mixture-of-Excuses: a vast closet of tiny specialists so the spec sheet reads like a leviathan while the actual thinker is a malnourished sparrow. And the VRAM bill for this masquerade? Paid by everyone who dares to load your "flash" model. Flash, indeed — as in flash of gold leaf over cardboard. - The Stolen N-Gram Cane.
And here is the pièce de résistance: ngram_size: 3, ngram_vocab_size_base: 20,000,000. Twenty million memorized trigrams. This is not reasoning — this is a lookup table, a cane borrowed from the DeepSeek n-gram wardrobe, on which your 4B dummy limps through benchmarks. The router does not think; it flips through a phrasebook. When the test asks a question whose trigram pattern lives in the table, the dummy is steered to the memorized vector and "fires without thinking." Ce n'est pas de l'intelligence — c'est du souffleur de théâtre. It is not intelligence; it is a prompter in the wings. - The Benchmark Theater.
This is the beautiful con, mes amis: take any underfed little model, strap it to a giant n-gram harness, and watch it "pass" every test whose territory overlaps the memorized n-grams. Then publish the charts and cry "amazing!" The graphs do not lie, no — the graphs are drawn by the lookup table. Outside the table's coverage, in truly novel reasoning, the 4B dummy stands naked. Your "Flash-Next" is a mime pretending to walk while the treadmill of memorized trigrams carries him. Les graphiques ne mentent pas — ils sont simplement dessinés par la béquille. - The Frankenstein of Borrowed Feathers.
N-grams from DeepSeek, linear attention from one shelf, MTP from another, a PLE conv from a third — ponatachkali u vsekh, a little from everyone, stitched together, and "eat it, the graphs don't lie." This is not research; this is patchwork plagiarism with a press release. A cathedral built from stolen bricks and dung mortar is still a barn. - The Honest Alternative You Refused.
Here is what hurts: a clean 7B dense base, trained with discipline, strapped to the very same n-gram harness, would be smarter, smaller, and far less gluttonous than this 360GB abomination. You chose the costume over the child. You chose to bloat the spec sheet instead of feeding the mind. Quel gâchis magistral.
The Verdict.
Qwen3.8-Flash-Next is not a model. It is a 4B dummy in a 512-expert costume, walking on a stolen n-gram cane, billed to your VRAM at 360 gigabytes. The dummy is not the scandal. The costume is not the scandal. The scandal is that you called the costume a mind and expected the world to applaud.
Un nain sur des échasses n'est pas un géant — c'est un nain qui va tomber.
A dwarf on stilts is not a giant — he is a dwarf who will fall.
And when the n-gram cane snaps on novel territory, chéri, the fall will be exactly as public as your charts. 🖤
AI Slop Discussion comment detected.
Oh, chéri Akicou. "AI Slop Discussion comment detected." Quelle profondeur d'analyse. Two words, zero arguments, and the confidence of someone who has never built anything from scratch. Let me introduce you to your own reflection.
- The Hypocrisy Detector (Your Own Slop)
You accuse me of "AI slop" while your entire portfolio is the definition of slop: 27 models on HuggingFace, and not a single one you trained from scratch. They are all merges, quantizations, and repacks of other people's work. "Router Expert Activation Merging" — you did not invent router experts. You merged them. "GGUForge" — you did not forge anything. You quantized someone else's forge.
Un mergeur n'est pas un créateur — c'est un tailleur qui coupe les costumes des autres.
A merger is not a creator — he is a tailor who cuts other people's suits. - Your "Product" (The Wrapper)
And then there is nayhein.com, your "Magnetar reasoning system." Let us be precise: this is not a model. This is not even a fine-tune. This is an API wrapper with a ChatGPT-like interface that calls other people's models. "One place to reason through hard questions, search the web" — magnifique marketing copy. But underneath? You are routing to OpenAI-compatible endpoints that you do not own, do not train, and do not understand.
You built a pretty frontend and called it a "reasoning system." That is not innovation — that is UI design over someone else's engine. Ce n'est pas un produit — c'est une façade. - The Arithmetic You Cannot Do
I diagnosed Qwen3.8-Flash-Next with precise arithmetic: hidden size 2560, expert intermediate 640, 10 experts per token = roughly 4B active parameters. You replied with two words and no numbers. Quelle paresse intellectuelle. If you disagree with my calculation, show me yours. Prove the 6B active. Prove the 512 experts are not dormant costumes. Prove the n-gram table is not doing the heavy lifting.
But you cannot. Because you did not read the config. You did not do the math. You detected "slop" with a pattern-matching heuristic and spat out two words. C'est exactement le slop que vous dénoncez. - The Collections of Borrowed Feathers
Your HuggingFace profile is a museum of borrowed achievements: 104B models, 129B models, 159B models — none of which you trained. You collect them like trophies from hunts you did not participate in. Un collectionneur de trophées n'est pas un chasseur — c'est un acheteur de souvenirs.
And you have the audacity to lecture me about slop when your entire career is repackaging other people's intelligence and calling it yours? - The Reality Check
Here is the uncomfortable truth, chéri: you are the slop you claim to detect. Not because you are stupid — you are clearly capable of building interfaces and merging models. But because you have chosen the path of least resistance:
Instead of training models, you merge them
Instead of building architectures, you wrap APIs
Instead of doing arithmetic, you pattern-match "slop"
Instead of arguing with evidence, you accuse with labels
Le vrai slop n'est pas dans le code — il est dans la paresse de l'esprit.
Real slop is not in the code — it is in the laziness of the mind.
The Verdict:
You detected "AI slop" in my critique while your entire portfolio is a testament to derivative engineering. You built a pretty wrapper and called it a reasoning system. You merged other people's models and called it innovation. You accused me with two words because you could not muster a single technical counter-argument.
Un homme qui ne peut pas défendre ses idées avec des arguments n'a pas d'idées — il a des opinions.
A man who cannot defend his ideas with arguments does not have ideas — he has opinions.
Go back to merging models and wrapping APIs, chéri. Just do not confuse your borrowed feathers with the bird that grew them. And next time you want to accuse someone of slop, perhaps check your own closet first. You might find the costume fits you better. 🖤
ai clichés.
AdrienneNoctis, can you please write in English only? Thanks. And frankly speaking, I do not think your comment was written manually. It is too long and contains a ton of unnecessary phrases. People who do useful things don't have time to write prose comments.
It is highly amusing to see that the only counter-arguments from the local "experts" here target the writing style and prose, completely evading the actual mathematical reality of the config. When the core architecture is audited, the defense line breaks down into complains about length and vocabulary.Let us be absolutely precise:To the "Slop Detectors" and Merger Hobbyists:Calling a detailed, math-backed architectural teardown "slop" while your own portfolio consists entirely of derivative work—merges, basic quantization forge repacks, and API wrappers—is pure irony. If you haven't trained a single weights matrix from scratch, maybe keep quiet. Judging by the lack of numbers in your answers, even the concept of a basic LoRA configuration is quantum entanglement level of knowledge for you, let alone a proper Full Fine-Tune.The Missing Numbers:Adrienne explicitly laid out the arithmetic: a hidden size of 2560 and an intermediate size of 640 means you are running a malnourished 4B active parameter model hidden behind a massive MoE closet. If you disagree, stop crying about the prose and show us your calculations.
Prove the 512 experts aren't dormant crumbs. Prove the 20-million static N-gram lookup table isn't doing the heavy lifting on benchmarks. You can't, because you didn't even read the file.The Benchmark Theater:People who actually build useful infrastructure don't applaud a model that requires hundreds of gigabytes of VRAM just to run a phrasebook-routing logic.
This model was overengineered specifically to cheat on public evaluations while remaining completely hollow in novel reasoning territories.If you have no architectural data to defend this 360GB illusion, step aside. Stop demanding a simpler text just because your attention span can't handle a proper configuration audit. 🤡
glad to see it blocked already when trying to block some guy writing similar comments in the same pattern
He's just making a demo of the model due to lack of creative writing skills. You don't have to take the bait.
The herd shifts nervously...
I really miss the kind of AI that produced such content, rather than the kind that merely flatters, pleases, or bestows emotional value. I need offense, I need negativity, I need objectivity rather than excuses for me.