Kimi K3 vs Qwopus3.8-27B-Flash-V2

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.

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.

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

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