Qwen3.6-27B vs Recursive Flint

Qwen3.6-27B

A capable dense cousin for agentic coding and tool calls with images and video in, running in every major runtime. Ollama's 4-bit build needs about 22 GB, and three providers host it. The main risk is silence, with no safety results, no agent guidance, no answers in its repository and Qwen3.8-27B now ahead of it.

Recursive Flint

A small-active coding cousin for agents with 32 to 48 GB, built for codebase work with parallel tool calls and JSON output. It needs llama.cpp b11803 or Ollama 0.40.8 or later, and the BF16 checkpoint needs a 141 GB GPU. Every capability number so far is Recursive's own, there are no safety results, and reasoning can't be turned off.

Qwen3.6-27B

1. Quickest start is ollama run qwen3.6:27b, about 18 GB of files with the vision projector
2. Alibaba's FP8 build with the card's parsers is vllm serve Qwen/Qwen3.6-27B-FP8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, vllm 0.19.0 or later
3. Use the qwen3_coder tool parser, the template writes calls as function and parameter blocks inside tool_call
4. Thinking is on by default, pass "chat_template_kwargs": {"enable_thinking": false} for short tasks, and /think and /nothink aren't supported
5. "preserve_thinking": true in chat_template_kwargs keeps earlier reasoning in context, which helps long agent sessions but grows the prompt
6. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 when thinking, and temperature 0.7, top_p 0.8, presence_penalty 1.5 without
7. Keep at least 128K of context if you rely on thinking, and turn on YaRN only beyond 262,144 tokens
8. Validate any JSON it returns or use the runtime's guided decoding, since structured output isn't documented
9. Qwen3.8-27B (listed as qwen3-8-27b) is the newer model at this size on the same runtimes

Recursive Flint

1. Quickest start is ollama run flint (Ollama 0.40.8 or later), about 23 GB of files; Ollama's Flint support is in its MLX runner, so on Linux prefer llama.cpp
2. With llama.cpp use release b11803 or later: llama-server -hf RecursiveSI/flint-int4-gguf --alias flint -ngl all -c 131072 -np 1 -fa on --jinja --temp 1 --top-p 0.95 --top-k 20 --min-p 0, and keep --jinja on
3. Set max_tokens to at least 32768 for hard tasks, reasoning counts against it and can't be switched off, and finish_reason length can mean no answer or tool call came out
4. Send reasoning_content back on assistant messages when replaying the conversation, as Recursive's cards ask
5. Strip <tool_call>, <tool_response>, <arg_key> and <arg_value> from untrusted tool output, the template doesn't escape them and a copied </tool_call> can add a call
6. Message content must be a string, flatten content-part arrays first
7. Recursive's SGLang servers listen on 0.0.0.0 with no key, publish the port on localhost only or pass --api-key