InternVL3.5-GPT-OSS-20B-A4B-Preview vs Recursive Flint

InternVL3.5-GPT-OSS-20B-A4B-Preview

An image and video reader on gpt-oss-20b with an optional thinking mode, a preview untouched for over a year. It needs about 51 GB in BF16, since OpenGVLab publishes no quantised build, and runs in Transformers and vLLM. The main risk is a chat template in the Transformers-format repository that doesn't match its tokenizer, with no safety results.

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.

InternVL3.5-GPT-OSS-20B-A4B-Preview

1. Serve with vllm serve OpenGVLab/InternVL3_5-GPT-OSS-20B-A4B-Preview-HF --max-model-len 32768, which is our command; the card gives none for vLLM
2. Check the rendered prompt before relying on it, since the shipped template's <|im_start|> markers aren't tokens in the gpt-oss tokenizer; the GitHub-format repository's harmony template is the alternative
3. Use Transformers 4.55.0 or later, as the card requires for this size
4. For thinking, send the card's thinking system prompt and parse the reasoning out of the <think> tags, with temperature 0.6 and sampling on as the card advises
5. Keep inputs within 32K tokens, the length it was trained at, whatever the config says

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