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

Recursive Flint vs ThinkingCap (Qwen3.8 27B)

Recursive Flint and ThinkingCap (Qwen3.8 27B) score within a point of each other on agent readiness, 61 (C) and 61 (C). 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

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 45
  • Agent interface, 90 against 70
  • Documentation and upkeep, 67 against 53

Also in its favour

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

Watch for

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

ThinkingCap (Qwen3.8 27B) C

Best for Small teams and individuals running Qwen3.8-27B for agent or reasoning work who want shorter thinking traces on one 24 GB GPU or Mac.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

PolyForm Small Business licence, free commercially only below 100 people and 1,000,000 USD (2019) revenue

Score by category

CategoryWeight this runRecursive FlintThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257575even
Risk20%206045Recursive Flint +15
Agent interface10%109070Recursive Flint +20
Documentation and upkeep10%106753Recursive Flint +14
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactRecursive FlintThinkingCap (Qwen3.8 27B)
KindOpen-weight modelOpen-weight model
VendorRecursiveBottleCap AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0PolyForm-Small-Business-1.0.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-212026-10-06
Terms last updatedno document linkedno document linked
Privacy policy last updatedno 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 reviews3.5/5 (4)2.5/5 (4)

Verdicts

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.

ThinkingCap (Qwen3.8 27B)

A Qwen3.8-27B with shorter reasoning, for agent work where thinking tokens cost time, and BottleCap's 4-bit GGUF runs in about 19 GB. The main limits are the licence, which needs a paid licence above 100 people or 1,000,000 USD revenue, a gated main repository, and no safety results or training-data description.

Before you call either

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

ThinkingCap (Qwen3.8 27B)

  1. Check the licence first, an organisation with 100 or more people or 1,000,000 USD (2019) revenue needs a commercial licence from BottleCap
  2. For files without the gate use llama-server -hf bottlecapai/ThinkingCap-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 17.4 GB
  3. On vLLM use --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_xml, and on SGLang --tool-call-parser qwen3_coder
  4. Set reasoning_effort (xhigh, medium or low) in chat_template_kwargs, any other value makes the template raise an error
  5. Keep the base's sampling (temperature 1.0, top_p 0.95, top_k 20), the GGUF card says greedy decoding can loop
  6. The GGUFs carry an MTP head, and llama.cpp builds without MTP support for this architecture may refuse to load them with a missing blk.64 tensor

Questions

Which is better for AI agents, Recursive Flint or ThinkingCap (Qwen3.8 27B)?

Recursive Flint and ThinkingCap (Qwen3.8 27B) score within a point of each other on agent readiness, 61 (C) and 61 (C).

Other comparisons with Recursive Flint or ThinkingCap (Qwen3.8 27B)

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.