Olmo 3 7B Think vs Recursive Flint

Olmo 3 7B Think

A fully open 7B reasoning cousin for maths, code and step-by-step answers, with every dataset and checkpoint published and its safety results rerunnable. Ollama's 4-bit build needs about 5.4 GB. It always thinks, wasn't trained for tool calls, has 65K of context, and Ai2 hasn't answered its discussions.

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.

Olmo 3 7B Think

1. Quickest start is ollama run olmo-3:7b-think, about 4.5 GB
2. With vLLM, vllm serve allenai/Olmo-3-7B-Think --max-model-len 65536; vLLM runs it through its Transformers backend
3. Sample at temperature 0.6 and top_p 0.95 with up to 32,768 output tokens, as the card recommends, since thinking traces are long
4. Every reply starts with a think block; strip it yourself or use a reasoning parser that reads think tags
5. Pass your own system prompt; the template's default says the cut-off is November 2024 and that no functions are available
6. For tool calls use Olmo 3 7B Instruct instead, which Ai2 trained for function calling
7. A discussion reports endless reasoning loops when served with vLLM, unanswered, so cap max_tokens
8. Check the use against Ai2's Responsible Use Guidelines, which bar automated social-media posting and undisclosed automated content outside research

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