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

Cosmos-Reason2-2B vs Ornith-1.5-397B

Cosmos-Reason2-2B and Ornith-1.5-397B score within a point of each other on agent readiness, 59.5 (C) and 59 (C). Ornith-1.5-397B leads on agent interface. Both do open-weight models you run yourself.

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

Which one, for what

Cosmos-Reason2-2B C

Best for Agents that need a small local model to reason over camera footage and images for robotics, driving or smart spaces

Ahead on

  • Risk, 60 against 50

Also in its favour

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

Watch for

Gated behind a click-through licence that needs a Hugging Face account

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

Ahead on

  • Agent interface, 85 against 65

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

Score by category

CategoryWeight this runCosmos-Reason2-2BOrnith-1.5-397BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256565even
Risk20%206050Cosmos-Reason2-2B +10
Agent interface10%106585Ornith-1.5-397B +20
Documentation and upkeep10%103936Cosmos-Reason2-2B +3
Negative events≤1500
TotalC 59.5/100C 59/100

Facts side by side

FactCosmos-Reason2-2BOrnith-1.5-397B
KindOpen-weight modelOpen-weight model
VendorNVIDIAOrnith
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceNVIDIA Open Model License (custom, commercial use allowed, not an OSI licence); built on Qwen3-VL-2B-Instruct under Apache 2.0MIT
Read-only variant documentednono
llms.txtnono
Last release2026-03-102026-08-23
Terms last updatedno 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.5/5 (4)2/5 (4)

Verdicts

Cosmos-Reason2-2B

A small local cousin for reasoning over video and images in robotics, driving and warehouse scenes, returning points, boxes and timed events as JSON. The 4.9 GB file runs in Transformers or vLLM, though NVIDIA asks for 24 GB of GPU memory. Development has moved to Cosmos 3, and the gated licence is revocable.

Ornith-1.5-397B

Ornith's flagship coding and terminal-agent cousin, 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 risk is an absent publisher, with no licence file, no safety results and files replaced without a note.

Before you call either

Cosmos-Reason2-2B

  1. Accept the licence on the Hugging Face card with a signed-in account and set HF_TOKEN before downloading
  2. Serve it with vllm serve nvidia/Cosmos-Reason2-2B --max-model-len 16384 --media-io-kwargs '{"video": {"num_frames": -1}}' --reasoning-parser qwen3, keeping max-model-len between 8,192 and 16,384 as NVIDIA advises
  3. For local video or images, make a folder for them (mkdir -p media) and pass --allowed-local-media-path "$(pwd)/media", so the server can read only that folder, not everything under the directory you start it from
  4. Sample video at 4 fps and allow at least 4,096 output tokens so the reasoning isn't cut off
  5. For reasoning, add the card's instruction to answer with a think block and then the answer; leave it out for a direct reply
  6. Use NVIDIA's prompt files (prompts/*.yaml in nvidia-cosmos/cosmos-reason2) when you want JSON boxes, events or trajectories, and validate the JSON yourself
  7. Check its plans before a robot acts on them, since NVIDIA's own safety card warns of collision and manipulation risks

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, Cosmos-Reason2-2B or Ornith-1.5-397B?

Cosmos-Reason2-2B and Ornith-1.5-397B score within a point of each other on agent readiness, 59.5 (C) and 59 (C). Ornith-1.5-397B leads on agent interface.

Other comparisons with Cosmos-Reason2-2B 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.