SAVRN
Search Contact SAVRN

Open-weight model · Text generation

halogen-qwen3.8-flash-next

by Peonist peonist-ai/halogen-qwen3.8-flash-next

Weights for dedicated inference engine for Qwen3.8-Flash-Next on AMD Strix Halo (gfx1151). One model family, one GPU, every kernel written for this silicon. These weights are in halogen's own.hgn format and will not load in transformers, vLLM, or llama.cpp.

Parameters
Context
Weights131.6 GB
Licenseapache-2.0
AccessOpen weights
Monthly Downloads

Model Card

By Peonist, published under apache-2.0, revision 0a3f13724b39.

Weights for dedicated inference engine for Qwen3.8-Flash-Next on AMD Strix Halo (gfx1151). One model family, one GPU, every kernel written for this silicon. These weights are in halogen's own.hgn format and will not load in transformers, vLLM, or llama.cpp. They exist to be mounted into the halogen-flash-server container. The checkpoint is TWO files. The sidecar is a patch overlay: a subset of tensors re-quantized more carefully, read in place of the base file's copies. The engine loads.overlay.hgn automatically when it sits beside the checkpoint, you do not configure anything, you just keep both files. Drop it and the model still runs, roughly 5–9% worse on perplexity, saying so in one…

Read Peonist's full model card

halogen-flash, Qwen3.8-Flash-Next for AMD Strix Halo

Weights for halogen-flash-server, a dedicated inference engine for Qwen3.8-Flash-Next on AMD Strix Halo (gfx1151). One model family, one GPU, every kernel written for this silicon.

These weights are in halogen's own .hgn format and will not load in transformers, vLLM, or llama.cpp. They exist to be mounted into the halogen-flash-server container.

What is here

qwen38-flash-next-w4b.hgn              115.55 GiB   checkpoint (1198 tensors)
qwen38-flash-next-w4b.overlay.hgn        2.40 GiB   quality sidecar, KEEP THIS
qwen38-flash-next-w4b.overlay-speed.hgn  2.31 GiB   optional: the speed arm
qwen38-flash-next-vision.hgn             0.84 GiB   optional: reads images
qwen38-flash-next-mtp.hgn                1.42 GiB   optional: the draft head, for running a GGUF
tokenizer/                                          flat tokenizer directory

The checkpoint is TWO files. The sidecar is a patch overlay: a subset of tensors re-quantized more carefully, read in place of the base file's copies. The engine loads <checkpoint>.overlay.hgn automatically when it sits beside the checkpoint, you do not configure anything, you just keep both files. Drop it and the model still runs, roughly 5–9% worse on perplexity, saying so in one line of startup output.

Download both. Together they are ~118 GiB, and the model needs ~68 GiB resident plus the memory-mapped n-gram table.

The vision file is separate and optional. qwen38-flash-next-vision.hgn lets the server read images, and without it the server is text-only and refuses an image with a message naming the setting that turns it on. Take it if you want to send screenshots; skip it and nothing else changes, because with no file the image path is absent rather than disabled and text behaviour is byte-identical either way. Put it beside the checkpoint and start the server with HALOGEN_VISION_TOWER=1.

The draft-head file is for running someone else's GGUF. Since 0.7.0 the server opens a llama.cpp GGUF of this model directly (unsloth's UD-IQ4_XS, or any llama-quantize output whose experts are IQ4_NL / IQ4_XS / IQ3_S / Q4_0 and whose dense layers are Q8_0), repacking it losslessly into RAM at startup. A GGUF carries no draft head this engine can run, so qwen38-flash-next-mtp.hgn supplies it: the checkpoint's own 31 head tensors, with the head's 18 dense projections at 8 bits as in the quality sidecar. With a GGUF the checkpoint and the two sidecars above are not needed at all, only this file and tokenizer/; the server fetches both when HALOGEN_DOWNLOAD names this repo. The server repository's README has what that path costs and buys, measured.

Plan on a machine of its own. Loaded at the defaults the server holds most of a 128 GB host, and what is left is mostly not in the large contiguous pieces another big process needs. If you run application containers or another model beside it they compete for the remainder, and when it runs out both they and the server can stop for minutes at a time at full CPU with no output, which is not a crash and needs no restart. The server reports what it leaves behind on its last line of startup, and the server repository has the settings that give memory back.

Use

hf download peonist-ai/halogen-qwen3.8-flash-next --local-dir ~/halogen-models

podman run --rm -p 8731:8731 \
  --device /dev/kfd --device /dev/dri --group-add keep-groups \
  --ipc=host --ulimit memlock=-1:-1 \
  -v ~/halogen-models:/models:ro \
  ghcr.io/peonist-ai/halogen-flash-server:0.11.6

This repo carries the tokenizer, so one -v is all you need. On Docker rather than Podman, replace --group-add keep-groups with --group-add video --group-add render: keep-groups is a Podman keyword that Docker resolves against the container's /etc/group and fails to find.

An OpenAI-compatible endpoint comes up on :8731: /v1/chat/completions, /v1/completions, /v1/models, and /v1/responses. The last of those is the Responses API, so the OpenAI Codex CLI works against this server directly, tool calls included, by pointing a model_providers entry at it with wire_api = "responses". Since 0.8.0 a response_format of json_schema or json_object (text.format on the Responses route) is enforced while the model decodes, so the reply is valid under the schema by construction, at no cost to speed. Since 0.9.0 an opt-in composable context preview (HALOGEN_COMPOSABLE_CONTEXT=1) lets a compacted conversation reuse its kept tool results without reading them again; it is off by default and not byte-identical (a reused answer is very close to, not the same as, reading the text fresh), so every exactness guarantee holds with it off. Since 0.9.1 the model's sparse-attention budget can be raised at startup (HALOGEN_INDEXER_BUDGET=4096, default 2048): in the server's retrieval battery 4096 recovered two planted facts at 16k that the default missed, for about 7% of prefill speed at 32k; off by default, and not byte-identical either.

Full documentation is in the server repository.

Precision

4-bit weights are a correctness precondition, not an optimization: Qwen3.8-Flash-Next is 125B total parameters plus a 51B n-gram embedding table, and neither BF16 (335 GiB) nor FP8 (173 GiB) fits in Strix Halo's 124 GB of unified memory. The question was never whether to quantize but where to spend the bits.

base file 115.55 GiB, 1198 tensors
trunk + experts Q4C-P (4-bit, per-column groups)
n-gram embedding table FP8, 47.7 GiB, a lookup, paged rather than resident
rank-1 / conv1d / PLE projections BF16 pass-through
quality sidecar 723 non-expert tensors re-quantized activation-aware, plus the twelve o_proj at 8-bit, plus (0.6.0) the MTP head's 18 dense projections at 8-bit

The sidecar is where most of the quality lives, and it is small because the loss was concentrated. Measuring each tensor family against its own BF16 ceiling put nearly all of the non-expert quantization cost in twelve o_proj tensors, 106 MB, 0.09% of the file. Those twelve now ship at 8 bits, which measures as a statistical tie with full BF16 rows. The mechanism is calibration: a 4-bit trunk is over-confident, and the whole gain sits in the hardest quartile of predictions.

0.6.0 adds the MTP head's own dense projections at 8 bits (18 tensors, 0.09 GiB) to both sidecars. They change no answer: the head only proposes tokens and the trunk verifies every one, so this is a speed change. Its proposals are accepted more often (51% to 59% on prose at the same trunk), which is worth about 4% of decode speed on prose and nothing on code. An older image reads the same file and gains the same; a 0.6.0 image with the older file says so at startup and, started with HALOGEN_DOWNLOAD set, fetches just this file.

Speculative decoding

The checkpoint carries the model's MTP head (a full Flash-Next layer , 512 experts and its own indexer). Speculative decoding with it is byte-identical to serial greedy decode: the head only proposes, and a token is emitted only if the trunk would have produced it. It is a speed optimization with no quality cost, on by default, and disableable per request.

Since 0.6.0 the server also drafts from the request's own text: when the last few tokens of the answer already occur earlier in the conversation, the tokens that followed them are proposed as a chain and verified in one step. Tool-call arguments, file paths and code that quotes the file being edited are mostly such copies, and that is where an agent's output spends its tokens. Same guarantee: every emitted token is the model's own greedy choice, and the same rule: it runs while the request is the only one generating.

Provenance and license

Derived from Qwen3.8-Flash-Next. These weights are a derivative work and are governed by the license of the original model, see the base model for those terms. Verify them yourself before commercial use; nothing here grants rights the upstream license does not. Unlike halogen's 27B checkpoint, no third-party quantization was imported: every quantized value here was produced by us from the BF16 originals.

The halogen-flash engine is separate, closed source, and distributed under its own terms, see the server repository.

"halogen" is a trademark of Peonist, LLC (U.S. application pending); see TRADEMARKS.md in the server repository for permitted use.

Identity and Version

Repository
peonist-ai/halogen-qwen3.8-flash-next
Publisher
Peonist
Task
Text generation
Modality
Text
Library
halogen
Parameters
Not stated by the source
Languages
moe, amd
Revision
0a3f13724b39b05e503c8cb1e08f78cd9cf6a5c0
First published
2026-09-01
Last updated
2026-09-18

Files and Weights

14 files, 131.6 GB in total.

Configuration1 file · 202 B
Tokenizer4 files · 22.9 MB
Documentation1 file · 9.5 KB
Other7 files · 131.5 GB
Repository1 file · 2.0 KB
Every file
FileTypeSizeSHA-256
tokenizer/generation_config.jsonConfiguration202 B
README.mdDocumentation9.5 KB
halogen.jpgOther250.6 KB 96542c8f6d06
qwen38-flash-next-mtp.hgnOther1.5 GB 0f50e9626df9
qwen38-flash-next-vision.hgnOther897.9 MB d62e0ae553fe
qwen38-flash-next-w4b.hgnOther124.1 GB 9c116bbc01f7
qwen38-flash-next-w4b.overlay-speed.hgnOther2.5 GB f49c8d14fa97
qwen38-flash-next-w4b.overlay.hgnOther2.6 GB 1cdfc3a9f988
tokenizer/chat_template.jinjaOther9.0 KB
.gitattributesRepository2.0 KB
tokenizer/merges.txtTokenizer3.4 MB
tokenizer/tokenizer.jsonTokenizer12.8 MB 0997f410c57a
tokenizer/tokenizer_config.jsonTokenizer17.9 KB
tokenizer/vocab.jsonTokenizer6.7 MB

License and Download

License
apache-2.0
Access
Open weights, no gate
Download from Peonist

Released by Peonist through its official repository on Hugging Face. Read the license.

Built From

Questions About halogen-qwen3.8-flash-next

Can I use halogen-qwen3.8-flash-next commercially?

Yes. halogen-qwen3.8-flash-next is released under Apache License 2.0. The Apache License 2.0 is a permissive open-source license. It permits commercial use, modification and redistribution. It requires keeping the license and copyright notices and any NOTICE file, stating significant changes, and it includes an express patent grant from contributors.

Similar Models

Fine-tune Qwen3 (14B) for free using our Google Colab notebook! - Read our Blog about Qwen3 support: unsloth.ai/blog/qwen3 - View the rest of our notebooks in our docs here. Qwen3-Coder is available in multiple sizes. Today, we're excited to introduce Qwen3-Coder-30B-A3B-Instruct. This streamlined model maintains impressive performance and efficiency, featuring the following key enhancements: - Significant Performance among open models on Agentic Coding, Agentic Browser-Use, and other foundational coding tasks. - Long-context Capabilities with native support for 256K tokens, extendable up to 1M tokens using Yarn, optimized for repository-scale understanding. - Agentic Coding supporting for…

Open weights apache-2.0 transformers

Model · Text generation

opt-125m

AI at Meta

OPT was first introduced in Open Pre-trained Transformer Language Models and first released in metaseq's repository on May 3rd 2022 by Meta AI. Disclaimer: The team releasing OPT wrote an official model card, which is available in Appendix D of the paper. Content from this model card has been written by the Hugging Face team. To quote the first two paragraphs of the official paper OPT was predominantly pretrained with English text, but a small amount of non-English data is still present within the training corpus via CommonCrawl. The model was pretrained using a causal language modeling (CLM) objective. OPT belongs to the same family of decoder-only models like GPT-3. As such, it was…

Open weights other 2,048 tokens transformers

Model · Text generation

Ornith-1.5-9B-GGUF

Ornith

Chirp Chirp! We are introducing Ornith-1.5, a major step toward building foundation models through end-to-end self-improvement. Ornith-1.5 extends Ornith-1.0 (which was developed on top of Qwen3.5 and Gemma4 with additional continued pretraining, mid-training, and post-training) by expanding the self-improvement loop from scaffold and rollout optimization to jointly optimizing task generation, scaffold construction, and solution rollouts. Rather than relying on a fixed set of human-curated tasks and manually designed harnesses, Ornith-1.5 continuously generates new training tasks, discovers effective strategies for solving them, and improves the policy through reinforcement learning. For…

Open weights mit transformers

Model · Text generation

Ornith-1.5-35B-A3B-GGUF

Ornith

Chirp Chirp! We are introducing Ornith-1.5, a major step toward building foundation models through end-to-end self-improvement. Ornith-1.5 extends Ornith-1.0 (which was developed on top of Qwen3.5 and Gemma4 with additional continued pretraining, mid-training, and post-training) by expanding the self-improvement loop from scaffold and rollout optimization to jointly optimizing task generation, scaffold construction, and solution rollouts. Rather than relying on a fixed set of human-curated tasks and manually designed harnesses, Ornith-1.5 continuously generates new training tasks, discovers effective strategies for solving them, and improves the policy through reinforcement learning. For…

Open weights mit transformers

Model · Text generation

Ornith-1.0-9B-GGUF

Ornith

Aloha! Today, we are releasing Ornith-1.0, a self-improving family of open-source models for agentic coding. This model card documents Ornith-1.0-9B, the most lightweight member of the Ornith family, designed for efficient single-GPU deployment. Ornith-1.0-9B is a dense ~9B model (≈19 GB in bf16), so it serves comfortably on a single 80GB GPU. The recipes below stand up an OpenAI-compatible server; add --tensor-parallel-size / --tp if you want to shard across more GPUs. For a quick local test (or to script offline generation), load the model directly with Transformers. Make sure you have a recent release installed — see the Transformers installation guide; Ornith-1.0-9B requires…

Open weights mit transformers

Uncensored Qwen3.8-27B, published as GGUF quantizations with the multi token prediction (MTP) head retained and verified. Refusal behaviour has been substantially reduced, not eliminated. See Measured behaviour for the numbers. Capabilities, training data, and architecture are otherwise unchanged. - Refusal directions removed with Heretic, which co minimizes refusal count against KL divergence from the base model. No handwritten refusal removal code, no finetuning, no additional training data. - Abliteration runs at bf16 (no 4 bit quantization). the resulting LoRA is merged into the bf16 base, so the published weights are not a quantized round trip. - mtp. tensors are copied verbatim from…

Open weights apache-2.0 llama.cpp