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

GLM-4.5-Air vs Recursive Flint

Recursive Flint scores 61 (C) on agent readiness against GLM-4.5-Air's 59.1 (C), and leads in 3 of 4 scored categories. GLM-4.5-Air leads on risk. 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

GLM-4.5-Air C

Best for Agents with two to four datacentre GPUs, or a provider account, who want a permissively licensed English and Chinese tool-calling model with wide runtime support.

Ahead on

  • Risk, 65 against 60

Watch for

Z.ai's smallest build is FP8 at about 135 GB in use, with no 4-bit build of its own

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

  • Reach, 75 against 65
  • Agent interface, 90 against 85
  • Documentation and upkeep, 67 against 38

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 runGLM-4.5-AirRecursive FlintEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256575Recursive Flint +10
Risk20%206560GLM-4.5-Air +5
Agent interface10%108590Recursive Flint +5
Documentation and upkeep10%103867Recursive Flint +29
Negative events≤1500
TotalC 59.1/100C 61/100

Facts side by side

FactGLM-4.5-AirRecursive Flint
KindOpen-weight modelOpen-weight model
VendorZ.ai (Zhipu AI)Recursive
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2025-08-112026-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

GLM-4.5-Air

An English and Chinese cousin for agent, coding and tool-calling work, with switchable thinking and wide runtime support. It needs about 135 GB for Z.ai's FP8 build, two to four H100s by Z.ai's figures, and Z.ai and Novita host it. The main risk is age, with files from August 2025 and no answers from Z.ai since.

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

GLM-4.5-Air

  1. Z.ai's FP8 recipe is python3 -m sglang.launch_server --model-path zai-org/GLM-4.5-Air-FP8 --tp-size 4 --tool-call-parser glm45 --reasoning-parser glm45, and 2 H100s are enough below the full 128K context
  2. Use the glm45 tool and reasoning parsers for this model, the glm47 parser in Z.ai's current README is for GLM-4.7
  3. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks, which makes the template add /nothink and an empty think block
  4. Declare tools in OpenAI style, and the template renders arguments as arg_key and arg_value pairs that the parser turns back into JSON
  5. Keep prompts under 128,000 tokens, the tokenizer config's limit, though config.json allows 131,072
  6. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented for the weights

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, GLM-4.5-Air or Recursive Flint?

Recursive Flint scores 61 (C) on agent readiness against GLM-4.5-Air's 59.1 (C), and leads in 3 of 4 scored categories. GLM-4.5-Air leads on risk.

Other comparisons with GLM-4.5-Air 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.