Agents-A1-4B vs Recursive Flint

Agents-A1-4B

A small agent cousin for search, research and tool-calling loops, with vision and 262,144 tokens of context. It runs in about 4 GB from InternScience's Q4_K_M GGUF, in vLLM, SGLang, Transformers or llama.cpp. The main risks are an undeclared base, no safety results or agent guidance, and a template that adds its own dated system prompt when you send none.

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.

Agents-A1-4B

1. Quickest start is llama-server -hf InternScience/Agents-A1-4B-Q4_K_M-GGUF --jinja, about 3.4 GB with the vision projector
2. With vLLM use --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, as on the card, and add --language-model-only for text-only work
3. Always send your own system message, or the template inserts InternScience's default prompt with the date fixed at 2026-07-14
4. The card recommends temperature 0.85, top_p 0.95, top_k 20, min_p 0 and presence_penalty 1.1, and there is no generation_config.json to set them
5. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
6. The config declares a multi-token prediction layer that isn't shipped, so don't turn on MTP speculative decoding
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