I've been maintaining my own chat template for Qwen3.8-Flash-Next, and after a discussion in another thread I decided to share it. I made a repo with my v1.4 template, the original Unsloth fixed stock template, and now a "Sharp" terseness mode version (based on /u/peculiar-ragdoll's original). The base is Unsloth's GGUF template, not froggeric's or Sharp's, because Flash-Next doesn't share a template with 27B. On top of Unsloth's template I fixed the requests that still fail or render badly: - Inline tags like set the effort level for clients that can't send template kwargs. - Repeated tool failures get escalating "diagnose first, then change course" notes. - Tool arguments passed as a JSON string render instead of killing the request. - Old turns no longer replay an empty block. - A stray with no opening tag gets split out instead of leaking into the answer. - Effort values like max, minimal and none no longer throw. Normal thinking-on history renders byte-for-byte what Unsloth's template renders, so the KV cache is reused and nothing changes when things are going well. For the Sharp version, I ported 27B Sharp's terseness block directly. This is what makes Tiel/Dirk/other models w/ the Sharp template respond less verbosely. It's appended after your system prompt, never replacing it. I kept Qwen's xhigh default instead of Sharp's medium. Terseness is a terse chat-template kwarg, on by default; {"terse": false} renders the v1.4 template normally, so you can A/B it on one server with no reload. Quick test: Flash-Next UD-Q5_K_XL on llama.cpp, xhigh effort, temp 1.0 / top-p 0.95 / top-k 20, 10 everyday prompts (explanations, advice, a coding request, a vague "can you help with my project?"): | | Answer tokens | Reasoning tokens | Wall time | |---|---|---|---| | Thinking on (16 pairs) | **−40%** (shorter in 13/16) | −8% (mixed) | −28% | | Thinking off (8 pairs) | **−61%** (shorter in 7/8) | n/a | −60% | Note: I personally leave the terseness setting off, as I found it does reduce accuracy somewhat, and just use a medium effort or switch to Swift-1.5-Flash-Next if I need a quicker response. However, I know a lot of people love Tiel/Dirk/Sharp, so since I'd already put up the repo, I figured I'd offer that option too. Any feedback or improvement suggestions are welcomed!   submitted by   /u/returnity [link]   [comments]