Ornith-1.5-397B vs Recursive Flint

Ornith-1.5-397B

Ornith's flagship coding and terminal-agent cousin, with XML tool calls that vLLM and SGLang parse and 262,144 tokens of context. It needs about 290 GB even at 4 bits, so a multi-GPU server, not the 128 GB reference machine. The main risk is an absent publisher, with no licence file, no safety results and files replaced without a note.

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.

Ornith-1.5-397B

1. Start it with the card's vLLM command at --tensor-parallel-size 8, or ollama run ornith-1.5:397b on a machine with about 300 GB of memory
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. When downloading the NVFP4 build, fetch only the files its model.safetensors.index.json names (the 25-shard set, 241.7 GB), not the eight extra shards
6. Pin a revision when you download, since Ornith has replaced files in place
7. Validate JSON output yourself, since structured output isn't documented

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