Ornith-1.5-9B vs Qwen3-Coder-Next

Ornith-1.5-9B

A small coding and terminal-agent cousin with thinking on by default, XML tool calls that vLLM and SGLang parse, and 262,144 tokens of context. Ornith's own 4-bit builds run in under 8 GB in most local runtimes. The main risk is an absent publisher, with no licence file, no safety results, files replaced without a note and no replies.

Qwen3-Coder-Next

A fast coding cousin for agent harnesses, with 3B active parameters and tool calling trained across many scaffold formats for Claude Code, Cline or Qwen Code loops. Alibaba's 4-bit GGUF needs about 58 GB, fitting one 64 GB machine, and two providers host it. The main risk is neglect, with no change since February, no replies and no safety results.

Ornith-1.5-9B

1. Start it with ollama run ornith-1.5:9b, or llama-server -hf ornith-ai/Ornith-1.5-9B-GGUF with the Q4_K_M file
2. In vLLM pass --enable-auto-tool-choice --tool-call-parser qwen3_xml --reasoning-parser qwen3, and in SGLang --tool-call-parser qwen3_coder --reasoning-parser qwen3, so tool calls and reasoning come back parsed
3. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
4. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
5. Use temperature 0.6, top_p 0.95, top_k 20 for coding and temperature 1.0 with presence_penalty 1.5 for general tasks, per the card
6. Pin a revision when you download, since Ornith has replaced files in place, and add mmproj-Ornith-1.5-9B-BF16.gguf (0.9 GB) for image input in llama.cpp
7. Validate JSON output yourself, since structured output isn't documented

Qwen3-Coder-Next

1. Quickest start is ollama run qwen3-coder-next (Q4_K_M, 52 GB of files)
2. On our reference machine Alibaba's Q8_0 GGUF (84.8 GB, about 102 GB in use) also fits, run with llama-server -m Qwen3-Coder-Next-Q8_0/Qwen3-Coder-Next-Q8_0-00001-of-00004.gguf --jinja -ngl 99 -fa on -c 131072
3. Serve with vllm serve Qwen/Qwen3-Coder-Next --enable-auto-tool-choice --tool-call-parser qwen3_coder (vLLM 0.15.0 or later), using the built-in parser rather than the repository's qwen3coder_tool_parser_vllm.py, which fails to import on newer vLLM per discussion 36
4. The card's commands use tensor parallel 2 though the text says 4 GPUs, and it suggests cutting the context to 32,768 if the server fails to start
5. There's no thinking mode, so don't pass enable_thinking or wait for reasoning_content
6. Sampling per the card is temperature 1.0, top_p 0.95 and top_k 40
7. The GGUF card's llama.cpp example path omits the quant from the file name; the real files are named like Qwen3-Coder-Next-Q4_K_M-00001-of-00004.gguf
8. Validate any JSON it returns, since structured output isn't documented