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

Qwen3-VL-8B-Instruct vs Recursive Flint

Recursive Flint scores 61 (C) on agent readiness against Qwen3-VL-8B-Instruct's 54.9 (C), and leads in 3 of 4 scored categories. Qwen3-VL-8B-Instruct leads on reach. 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

Which one, for what

Qwen3-VL-8B-Instruct C

Best for An agent with 8 GB or more to spare that needs a local model to read images, documents and video

Ahead on

  • Reach, 100 against 75

Watch for

No safety evaluation, agent-use guidance or security contact

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 55
  • Agent interface, 90 against 60
  • Documentation and upkeep, 67 against 31

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 runQwen3-VL-8B-InstructRecursive FlintEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%2510075Qwen3-VL-8B-Instruct +25
Risk20%205560Recursive Flint +5
Agent interface10%106090Recursive Flint +30
Documentation and upkeep10%103167Recursive Flint +36
Negative events≤1500
TotalC 54.9/100C 61/100

Facts side by side

FactQwen3-VL-8B-InstructRecursive Flint
KindOpen-weight modelOpen-weight model
VendorAlibaba (Qwen team)Recursive
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2025-11-012026-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

Qwen3-VL-8B-Instruct

A small vision-language cousin for reading screenshots, documents, charts and video, in about 6 GB from Alibaba's Q4_K_M GGUF and every major runtime, under plain Apache 2.0. It has no thinking mode and documents tool calls only in the template. The main risk is no published safety work, so add your own guardrails before it drives a GUI.

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

Qwen3-VL-8B-Instruct

  1. Start it with llama-server -hf Qwen/Qwen3-VL-8B-Instruct-GGUF:Q4_K_M --jinja -c 32768, or ollama run qwen3-vl:8b-instruct
  2. In Ollama the plain qwen3-vl:8b tag is the Thinking edition, so name 8b-instruct
  3. With the GGUF, load the mmproj vision file too, or images won't be read
  4. Parse tool calls as JSON inside <tool_call> tags, or use SGLang's --tool-call-parser qwen
  5. Use the card's sampling, temperature=0.7, top_p=0.8, top_k=20, presence_penalty=1.5 for vision and temperature=1.0, top_p=1.0, top_k=40, presence_penalty=2.0 for text
  6. Validate JSON output yourself, since structured output isn't documented
  7. vLLM needs 0.11.0 or later and Transformers 4.57.0 or later

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, Qwen3-VL-8B-Instruct or Recursive Flint?

Recursive Flint scores 61 (C) on agent readiness against Qwen3-VL-8B-Instruct's 54.9 (C), and leads in 3 of 4 scored categories. Qwen3-VL-8B-Instruct leads on reach.

Other comparisons with Qwen3-VL-8B-Instruct 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.