Kimi K3 vs Swift 1.5 Qwen3.8-Flash-Next

Kimi K3

Kimi K3 is a 2.8T multimodal agent model with a 1M-token context, parallel tool calls and per-request effort, for long coding and research sessions. Its 1,561 GB of files need a multi-node GPU cluster, so most agents will call a hosted copy. The main risks are Moonshot's Python running at load and prompt time, and no answers in its repository.

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.

Kimi K3

1. Start it with SGLang on a node of 8 B300s, sglang serve --trust-remote-code --model-path moonshotai/Kimi-K3 --tp-size 8 --context-length 65536 --mem-fraction-static 0.82 --reasoning-parser kimi_k3 --tool-call-parser kimi_k3 --port 30000
2. Use the kimi_k3 tool-call and reasoning parsers in vLLM or SGLang, and validate tool-call arguments against the schema, since vLLM's recipe says K3 sometimes emits a format its parser doesn't expect
3. Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
4. Thinking is always on; set reasoning_effort to low or high when max is too slow
5. Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
6. Don't hand an ongoing session from another model to K3, and state boundaries in the system prompt, since Moonshot warns it can act on its own when intent is unclear
7. Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page

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