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

Ornith-1.5-122B vs Ornith-1.5-397B

Ornith-1.5-122B scores 61 (C) on agent readiness against Ornith-1.5-397B's 59 (C), and leads in 1 of 4 scored categories. 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

  • Reach, 75 against 65

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

Ornith-1.5-397B C

Best for A self-hosted frontier-scale coding agent on an 8-GPU server, where a clear licence file and an answering publisher aren't required

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

Watch for

Needs about 290 GB of memory at 4 bits and about 970 GB in BF16, so it doesn't fit the reference machine

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.

Reach Ornith-1.5-122B +10

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.

Ornith-1.5-397B 65

Memory 0, since the smallest 4-bit build, Ollama's at 242 GB, needs about 290 GB with the fifth added, above the 256 GB band, and Ornith's own Q4_K_M GGUF and NVFP4 builds need about the same. Runtimes 25, the most the line gives, from vLLM 0.19.1, SGLang 0.5.9, Transformers 5.8.1, llama.cpp's qwen35moe architecture and Ollama's library, while LM Studio's entry is the base's. Builds 15, Ornith publishes FP8, NVFP4 and GGUF at several precisions. Terms 15, MIT as named in the card's metadata on 21 October 2026, 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.

Score by category

CategoryWeight this runOrnith-1.5-122BOrnith-1.5-397BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257565Ornith-1.5-122B +10
Risk20%205050even
Agent interface10%108585even
Documentation and upkeep10%103636even
Negative events≤1500
TotalC 61/100C 59/100

Facts side by side

FactOrnith-1.5-122BOrnith-1.5-397B
KindOpen-weight modelOpen-weight model
VendorOrnithOrnith
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITMIT
Read-only variant documentednono
llms.txtnono
Last release2026-10-242026-08-23
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2/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.

Ornith-1.5-397B

Ornith's largest coding and terminal-agent model, with XML tool calls that vLLM and SGLang parse and 262,144 tokens of context. It needs about 290 GB even at 4 bits, so a multi-GPU server, not the 128 GB reference machine. The main risks are a missing licence file, no safety results, no publisher replies and files replaced without a note.

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

Ornith-1.5-397B

  1. Start it with the card's vLLM command at --tensor-parallel-size 8, or ollama run ornith-1.5:397b on a machine with about 300 GB of memory
  2. 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
  3. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  4. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
  5. When downloading the NVFP4 build, fetch only the files its model.safetensors.index.json names (the 25-shard set, 241.7 GB), not the eight extra shards
  6. Pin a revision when you download, since Ornith has replaced files in place
  7. Validate JSON output yourself, since structured output isn't documented

Questions

Which is better for AI agents, Ornith-1.5-122B or Ornith-1.5-397B?

Ornith-1.5-122B scores 61 (C) on agent readiness against Ornith-1.5-397B's 59 (C), and leads in 1 of 4 scored categories.

Other comparisons with Ornith-1.5-122B or Ornith-1.5-397B

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.