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

Ornith-1.5-122B vs Qwen3-VL-4B-Instruct

Ornith-1.5-122B scores 61 (C) on agent readiness against Qwen3-VL-4B-Instruct's 52.6 (D), and leads in 2 of 4 scored categories. Qwen3-VL-4B-Instruct leads on reach and risk. Both do open-weight models you run yourself.

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

Which one, for what

Ornith-1.5-122B C

Best for Local coding and terminal agents on a 128 GB unified-memory machine or a 96 GB GPU setup, where a clear licence file and an answering publisher aren't required

Ahead on

  • Agent interface, 85 against 60
  • Documentation and upkeep, 36 against 31

Watch for

No LICENSE file though the card links one, and no notice for the Apache 2.0 Qwen3.5 and Gemma 4 work it builds on

Qwen3-VL-4B-Instruct D

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

Ahead on

  • Reach, 95 against 75
  • Risk, 55 against 50

Watch for

No safety evaluation, agent-use guidance or security contact

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent interface Ornith-1.5-122B +25

Ornith-1.5-122B 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card shows how tools go in and how calls come back and names the parser for vLLM and SGLang. Trained tool calling 20, Ornith trains it on agent tasks and the template renders several calls in one turn. Structured output 0, not documented or claimed. Reasoning control 10, Ornith's template reads enable_thinking per request and the card says the reasoning comes back in reasoning_content, though the card doesn't name the switch. Context 10, 262,144 tokens native.

Qwen3-VL-4B-Instruct 60

A Jinja chat template in the repository (20). The tool-call format lives only in the template, Hermes-style JSON in tool_call tags, and Alibaba names no parser (10). Trained for function calling with several calls allowed in a turn, per the family's technical report (20). No documented structured output (0). No thinking mode in this edition, so reasoning control scores 0 by the rule. 262,144 tokens of native context (10). 20+10+20+0+0+10 = 60.

Reach Qwen3-VL-4B-Instruct +20

Ornith-1.5-122B 75

Memory 10, since Ornith's own MLX 4-bit build is 69.7 GB and needs about 83.6 GB with the fifth added, over 64 GB and inside the reference machine's 107.4 GB, as do its Q4_K_M GGUF, its NVFP4 build and Ollama's build. Runtimes 25, the most the line gives, from vLLM 0.33.0, SGLang 0.5.23, Transformers 5.22.2, llama.cpp's qwen35moe architecture, Ollama's library and LM Studio's catalogue for the qwen35moe architecture. Builds 15, Ornith publishes FP8, NVFP4, GGUF and MLX at several precisions. Terms 15, MIT as named in the card's metadata, with nothing added, read by its terms though the repository has no licence file. Download 10, nothing is gated. Hosted 0, Ornith runs no API and no inference provider serves it. 10 + 25 + 15 + 15 + 10 + 0 = 75.

Qwen3-VL-4B-Instruct 95

Alibaba's own Q4_K_M GGUF with its vision file is 2.95 GB, so with a fifth added it needs about 3.5 GB and fits well within 16 GB (30). Transformers 4.57.0, vLLM, SGLang and llama.cpp run it in released versions, and Ollama through its pinned llama.cpp build, which reaches the 25 cap (25). Alibaba publishes FP8 and GGUF builds at F16, Q8_0 and Q4_K_M (15). Apache 2.0 with nothing added (15). No gate and no account (10). Only Featherless is live in the Hub's provider mapping, so it isn't hosted too (0). 30+25+15+15+10+0 = 95.

Risk Qwen3-VL-4B-Instruct +5

Ornith-1.5-122B 50

File safety 25, safetensors and GGUF only and no Python in any of Ornith's repositories for this size, so the card's --trust-remote-code flag loads nothing from the repository. Provenance 15, the files come from the ornith-ai organisation Ornith's blog links to, with a SHA-256 for every weight file. Safety evaluation 0 and agent guidance 0, nothing published on either. Licence risk 10, MIT carries no policy, threshold or changeable terms, but the card's licence link is broken. Security programme 0, no security.txt, disclosure policy or security contact.

Qwen3-VL-4B-Instruct 55

Safetensors and GGUF only and no code in the repositories, so the FP8 card's trust_remote_code flag runs nothing (25). Files in the Qwen organisation with a checksum on every file (15). No safety evaluation at all (0). No guidance for agent use, which matters for a model sold as a GUI agent (0). Apache 2.0 carries none of the licence risks (15). No security contact, disclosure policy or public advisories found for Qwen (0), and Alibaba's group-wide security centre wasn't checked. 25+15+0+0+15+0 = 55.

Documentation and upkeep Ornith-1.5-122B +5

Ornith-1.5-122B 36

Model card 11, it covers intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off. Training data 5, a description of the method with no data or cut-off. Last change 20, a folder upload to the MLX builds on 24 October 2026, 17 days ago. Responsiveness 0, Ornith answered none of the 5 questions and reports. Version policy 0, the MLX builds were uploaded a second time four days after the first with no note. File health 0, the card links a missing LICENSE, states hardware its own files don't fit and names a variant that doesn't exist, and the two chat templates differ. 11 + 5 + 20 + 0 + 0 + 0 = 36.

Qwen3-VL-4B-Instruct 31

The card misses limitations, languages and a cut-off (11). Training data is described only in the technical report, with no cut-off (5). The last change to code that runs it was the qwen-vl-utils fix of 4 January 2026, and the weights haven't changed since November 2025 (5). Qwen answered none of the 14 Hugging Face discussions that aren't pull requests, counted on 4 November 2026 (0), and GitHub issues weren't counted. Earlier versions kept in their own repositories without notes (5). Two reports wait without a reply (5). 11+5+5+0+5+5 = 31.

Score by category

CategoryWeight this runOrnith-1.5-122BQwen3-VL-4B-InstructEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257595Qwen3-VL-4B-Instruct +20
Risk20%205055Qwen3-VL-4B-Instruct +5
Agent interface10%108560Ornith-1.5-122B +25
Documentation and upkeep10%103631Ornith-1.5-122B +5
Negative events≤1500
TotalC 61/100D 52.6/100

Facts side by side

FactOrnith-1.5-122BQwen3-VL-4B-Instruct
KindOpen-weight modelOpen-weight model
VendorOrnithAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-242025-11-01
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/5 (4)

Verdicts

Ornith-1.5-122B

The largest Ornith that fits a 128 GB machine, a coding and terminal-agent cousin on Qwen3.5-122B-A10B's architecture with XML tool calls and 262,144 tokens of context. Its 4-bit builds need 84 to 93 GB. The main risk is an absent publisher, with no licence file, safety results or replies, and a card that misstates the hardware.

Qwen3-VL-4B-Instruct

Qwen3-VL-4B-Instruct reads screenshots, documents, charts and video, and Alibaba's Q4_K_M GGUF needs about 3.5 GB. Transformers, vLLM, SGLang, llama.cpp and Ollama run it under plain Apache 2.0. It has no thinking mode, documents tool calls only in the template, and Qwen hasn't answered repository questions or published safety work, so add guardrails before it drives a GUI.

Before you call either

Ornith-1.5-122B

  1. Start it with ollama run ornith-1.5:122b-q4_K_M, or llama-server -hf ornith-ai/Ornith-1.5-122B-GGUF:Q4_K_M --jinja -c 262144
  2. Budget about 92 GB for the Q4_K_M GGUF with a working context, and less context if the machine has under 100 GB for the model
  3. In vLLM pass --enable-auto-tool-choice --tool-call-parser qwen3_xml --reasoning-parser qwen3, and in SGLang --tool-call-parser qwen3_coder --reasoning-parser qwen3, so tool calls and reasoning come back parsed
  4. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  5. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
  6. Use temperature 0.6, top_p 0.95, top_k 20 for coding and temperature 1.0 for general tasks, as the card recommends
  7. Add mmproj-Ornith-1.5-122B-BF16.gguf (0.9 GB) for image input in llama.cpp, and validate JSON output yourself, since structured output isn't documented

Qwen3-VL-4B-Instruct

  1. Start it with llama-server -hf Qwen/Qwen3-VL-4B-Instruct-GGUF:Q4_K_M --jinja -c 32768, or ollama run qwen3-vl:4b-instruct
  2. In Ollama the plain qwen3-vl:4b tag is the Thinking edition, so name 4b-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

Questions

Which is better for AI agents, Ornith-1.5-122B or Qwen3-VL-4B-Instruct?

Ornith-1.5-122B scores 61 (C) on agent readiness against Qwen3-VL-4B-Instruct's 52.6 (D), and leads in 2 of 4 scored categories. Qwen3-VL-4B-Instruct leads on reach and risk.

Other comparisons with Ornith-1.5-122B or Qwen3-VL-4B-Instruct

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.