Apodex-1.1-mini vs Qwen3.8-Flash-Next

Apodex-1.1-mini

An agent cousin fine-tuned from Qwen3.5-35B-A3B for long tasks with files, code and tools, with parallel tool calling and about 3B active parameters. It needs 32 GB for Apodex's GGUF, NVFP4 or GPTQ-Int4 builds or about 86 GB in BF16, and Apodex's API serves it too. The main risks are no safety results and no replies from the publisher.

Qwen3.8-Flash-Next

A large sparse cousin with 6B active parameters for agentic coding and multimodal work, previewing Qwen's next architecture. It needs a 128 GB Mac for Ollama's MLX build or about 144 GB for the 4-bit GGUF, and Qwen Cloud serves it. The main risk is a licence that needs a separate deal for hosted-model and coding or office assistant businesses.

Apodex-1.1-mini

1. Serve it with vllm serve apodex/Apodex-1.1-mini --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser qwen3, or the same parsers in SGLang, so tool calls and reasoning come back parsed
2. For llama.cpp, llama-server -hf apodex/Apodex-1.1-mini-GGUF:Q4_K_M --jinja --reasoning-format deepseek, and the card passes the repository's chat_template.jinja with --chat-template-file
3. Pass tools through the API's tools parameter rather than in the system prompt, as the card asks
4. The card recommends temperature 1.0, top_p 0.95, repetition_penalty 1.05 and max_tokens up to 32,768
5. Send your own system prompt, or set identity_mode, since the template otherwise adds an Apodex identity block
6. The template keeps all earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
7. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
8. The card's Python example has a broken line where it runs the tool (available_toolsname), so fix it to available_tools[name](**args) before running
9. Validate JSON output yourself, since structured output isn't documented

Qwen3.8-Flash-Next

1. On a 128 GB Mac start it with ollama run qwen3.8-flash-next:125b-mlx (105 GB, NVFP4), on Linux the smallest Ollama build is qwen3.8-flash-next:125b-a6b-q4_K_M at 120 GB, which won't fit a 107.4 GB GPU share
2. On a server, vllm serve Qwen/Qwen3.8-Flash-Next-FP8 --tensor-parallel-size 4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as Qwen's GitHub README does
4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false to skip it, and read the reasoning from reasoning_content, even though SGLang's cookbook says thinking can't be turned off
5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
6. Send at most one system message and put it first, since the template raises an error otherwise
7. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
8. vLLM keeps the 51B n-gram table in host memory on 80 GB GPUs by default, per its recipe
9. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
10. Read the Qwen Community License before serving it to others as an API or inside a coding or office assistant product