Hy3 vs Qwopus3.8-27B-Flash-V2

Hy3

Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies since July.

Qwopus3.8-27B-Flash-V2

A Qwen3.8-27B cousin tuned to think less per turn in long agent loops, with an MTP head for speculative decoding in llama.cpp. It fits 24 GB with Jackrong's 4-bit GGUF. The risks are one person's experimental release with no safety work, training traces taken from Claude and GPT, and a tool format that differs from Qwen's.

Hy3

1. Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
2. In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
3. Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
4. With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
5. Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
6. Use temperature 0.9 and top_p 1.0, the card's recommended sampling
7. On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
8. Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers

Qwopus3.8-27B-Flash-V2

1. Quickest start is llama-server -hf Jackrong/Qwopus3.8-27B-Flash-V2-GGUF:Q4_K_M --jinja, about 17 GB, and add mmproj-F32.gguf for images
2. The card's tests used Q5_K_M with the bundled MTP head and --spec-type draft-mtp in llama.cpp
3. The template asks for tool calls as JSON inside tool_call tags, so use a Hermes-style parser (vLLM's hermes), not Qwen3.8's qwen3_coder
4. For coding the card recommends enable_thinking true, reasoning_effort xhigh and temperature 0.3, which you must pass yourself, since generation_config.json says 1.0
5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
6. Earlier reasoning stays in the context unless preserve_thinking is false
7. Cap max_tokens, since a report says it loops more than V1