GLM-5.3 vs Swift 1.5 Qwen3.8-Flash-Next

GLM-5.3

A large coding and long-horizon agent model with a 1M-token context, several tool calls per turn and three reasoning budgets. Z.ai's smallest build is 756 GB in FP8, so it needs an 8-GPU server, Z.ai's API or a provider. The main risks are no published safety work, no way to report a flaw, and thinking that can't be turned off.

Swift 1.5 Qwen3.8-Flash-Next

A large mixture-of-experts cousin, Qwen3.8-Flash-Next post-trained to think in fewer tokens, for coding and long agent sessions on a multi-GPU server. Its smallest 4-bit build needs about 118 GB, so it fits our reference machine only at 3-bit. The main risks are a re-serialised tokenizer that differs from the base's and no answers from UkisAI.

GLM-5.3

1. Start it with vllm serve zai-org/GLM-5.3 --kv-cache-dtype fp8 --tensor-parallel-size 8 --speculative-config.method mtp --speculative-config.num_speculative_tokens 5 --tool-call-parser glm47 --reasoning-parser glm47 --enable-auto-tool-choice --served-model-name glm-5.3 (vLLM 0.28.0 or later, 8xH200 or 8xH20 per vLLM's recipe)
2. Use the glm47 tool-call and reasoning parsers in vLLM or SGLang; SGLang's cookbook says glm45 leaves the calls as plain text
3. Pass chat_template_kwargs: {"reasoning_effort": "low"} for short tasks; anything other than low or high falls back to max
4. Pass clear_thinking: true in chat use, since the template keeps earlier reasoning by default
5. Don't send enable_thinking: false; the template ignores it and always opens a think block
6. Validate JSON output yourself, since structured output is documented only for Z.ai's hosted API
7. No Z.ai build fits a 128 GB machine; the full 1M context needs 8xB200 per vLLM's recipe

Swift 1.5 Qwen3.8-Flash-Next

1. On a multi-GPU node use vllm serve ukisai/Swift1.5-Qwen3.8-Flash-Next --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parser the base's recipes and the card's SGLang command use
2. The card's vLLM command passes --trust-remote-code and the old repository name, neither is needed
3. On our reference machine only UkisAI's GSQ-RCO IQ3_S GGUF (84.7 GB with the projector) fits, below 4-bit
4. Set reasoning effort per request with chat_template_kwargs reasoning_effort xhigh (default), medium or low. UkisAI's own runs lose about 2.5 points at medium and low
5. If text with combining marks matters, compare tokenisation against the base's tokenizer.json before trusting outputs
6. Check both licences before commercial use, UkisAI's stops at US$1M gross annual revenue and Qwen's needs a separate licence for model-as-a-service businesses