Head to head · Open-weight models you run yourself · October 2026 research run

MiniCPM-o 4.5 vs Recursive Flint

MiniCPM-o 4.5 and Recursive Flint score within a point of each other on agent readiness, 61 (C) and 61 (C). Recursive Flint leads on risk and agent interface. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 3023 open weights comparisons

Best conversational voice-agent APIs · All 392 voice agents comparisons

Which one, for what

MiniCPM-o 4.5 C

Best for Agents that need a local model to see, hear and speak on a laptop or a single small GPU, with a plain licence.

Ahead on

  • Reach, 90 against 75

Watch for

Speech output and full duplex need trust_remote_code with Transformers 4.51.0 or OpenBMB's llama.cpp-omni

Recursive Flint C

Best for Agents doing repository work on a 32 to 48 GB Mac or NVIDIA box that want a fast sparse coder with documented tool calls and a plain licence.

Ahead on

  • Risk, 60 against 40
  • Agent interface, 90 against 35

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.8 out of 5

Watch for

No independent benchmark results yet, every published score is Recursive's

Score by category

CategoryWeight this runMiniCPM-o 4.5Recursive FlintEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259075MiniCPM-o 4.5 +15
Risk20%204060Recursive Flint +20
Agent interface10%103590Recursive Flint +55
Documentation and upkeep10%106667Recursive Flint +1
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactMiniCPM-o 4.5Recursive Flint
KindOpen-weight modelOpen-weight model
VendorOpenBMBRecursive
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0; built from Qwen3-8B, SigLIP2, Whisper-medium and CosyVoice2, all Apache 2.0 on their Hub cardsApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-162026-10-21
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.8/5 (4)3.5/5 (4)

Verdicts

MiniCPM-o 4.5

A small omni cousin that sees, listens and talks back, with full-duplex speech and voice cloning, in about 7 GB at 4-bit through llama.cpp or Ollama for text and images. Speech output needs OpenBMB's remote code or llama.cpp-omni, and 28 GB of GPU for the full demo. The main risks are repository code and pickle files and 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.

Before you call either

MiniCPM-o 4.5

  1. Quickest start for text and images is ollama run openbmb/minicpm-o4.5, about 6 GB
  2. With vLLM 0.16.0 or later pass --trust-remote-code, and send stop_token_ids [151643, 151645] as OpenBMB's guide does
  3. vLLM, llama.cpp and Ollama return text only; for speech out use the card's Transformers 4.51.0 code or OpenBMB's llama.cpp-omni
  4. In llama.cpp pass both the language GGUF and MiniCPM-o-4_5-vision-F16.gguf with --mmproj, and use --jinja --reasoning-budget 0 to turn thinking off
  5. Keep prompts within 40,960 tokens
  6. Don't rely on tool calls or JSON output, neither is documented; validate any you get

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

Questions

Which is better for AI agents, MiniCPM-o 4.5 or Recursive Flint?

MiniCPM-o 4.5 and Recursive Flint score within a point of each other on agent readiness, 61 (C) and 61 (C). Recursive Flint leads on risk and agent interface.

Other comparisons with MiniCPM-o 4.5 or Recursive Flint

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.