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

Cosmos-Reason2-2B vs Ripple-65B Preview

Cosmos-Reason2-2B scores 59.5 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 2 of 4 scored categories. Ripple-65B Preview leads on agent interface and documentation and upkeep. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 3674 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

  • Reach, 65 against 45
  • Risk, 60 against 55

Watch for

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

Ripple-65B Preview D

Best for Teams with Blackwell GPUs or a DGX Spark who want an Apache 2.0 coding model to try for terminal and agentic coding work, and can run the publisher's code to serve it.

Ahead on

  • Agent interface, 75 against 65
  • Documentation and upkeep, 49 against 39

Watch for

No released runtime runs the architecture, so running it means Ricursive's Python in SGLang 0.5.19 or Transformers' remote code

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 Cosmos-Reason2-2B +20

Cosmos-Reason2-2B 65

Memory earns the full 30 because the BF16 file is 4.9 GB, about 5.9 GB with the fifth added, though NVIDIA itself asks for 24 GB of GPU memory. Runtimes get 20 because the model keeps Qwen3-VL's architecture, which Transformers, vLLM, SGLang and llama.cpp run in released versions, while LM Studio's catalogue has only the base. Builds score 0, as NVIDIA publishes no quantised build of the 2B. The NVIDIA Open Model License allows free commercial use under a use policy (10). The gate is an automatic click-through that needs an account (5), and nothing hosts the 2B (0).

Ripple-65B Preview 45

Memory 10 of 30, the smallest 4-bit build is Ricursive's NVFP4 at 57.2 GB, 68.7 GB with a fifth added, which is over 64 GB and fits our reference machine. Runtimes 0, no released runtime runs the ricursive architecture with its own code; Ricursive's SGLang plugin and Transformers' remote code don't count. Builds 10, one quantised precision (NVFP4) from Ricursive. Terms 15, Apache 2.0 with nothing added. Download 10, not gated. Hosted 0, Ricursive serves no API, Hugging Face maps no provider, Together AI's page says coming soon, and GMI Cloud's and OpenRouter's pages weren't read.

Agent interface Ripple-65B Preview +10

Cosmos-Reason2-2B 65

A Jinja template ships as chat_template.json (20). Tools are declared only by the template it inherits from Qwen3-VL, with no NVIDIA documentation or parser (10), and nothing shows the 2B was trained for tool use (0). NVIDIA's prompt files ask for JSON with named keys for boxes, events and trajectories (15). Reasoning is asked for in the prompt and vLLM's qwen3 parser returns it apart (10). The card states 256K input tokens (10).

Ripple-65B Preview 75

Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, Ricursive's server README says how tools are declared and calls come back, with the ripple parser in SGLang 0.5.19. Trained tool calling 20, one or more calls a turn and agentic-coding RL. Structured output 0, not documented. Reasoning control 0, the template has no thinking switch or effort levels. Context 10, long-context training at 2M-token sequences for a stated 1M.

Documentation and upkeep Ripple-65B Preview +10

Cosmos-Reason2-2B 39

The card misses languages and a cut-off (14). Training data is named by dataset without sizes or a cut-off (5). The Hub repository last changed on 30 April 2026, 188 days before this check, which alone gives 5. NVIDIA's GitHub repository last changed with a README redirect to Cosmos 3 on 7 June 2026, 150 days back, and this run counts the publisher's documentation commits on this line (10). None of its 3 discussions has an NVIDIA reply, counted by author flags on 4 November (0). The 2B's weights were replaced in place in March with a dated line, and the family is now superseded by Cosmos 3 with a dated note (5). The gated files couldn't be checked against the card, which itself mixes float16 and BF16 and links a newer licence than the gate shows (5). 14 + 5 + 10 + 0 + 5 + 5 = 39.

Ripple-65B Preview 49

Model card 14 of 20, no limitations and no knowledge cut-off. Training data 5, a general description with token counts and no cut-off. Last change 20, released today. Responsiveness 0, no discussions yet, read as none answered. Version policy 5, a first release, with the NVFP4 checkpoint replaced in place on release day under a commit note. File health 5, tokenizer_config.json carries a second, tool-less chat template and a 131,072-token limit against the card's 1M.

Risk Cosmos-Reason2-2B +5

Cosmos-Reason2-2B 60

File safety gets the full 25, one safetensors file loaded by Transformers' own code with a template, no remote code. Provenance gets 15 for files in NVIDIA's own organisation with hashes. The licence has a use policy and guardrail clause and NVIDIA can revoke or update it, so licence risk keeps 5 of 15. NVIDIA's PSIRT route and bulletins give the security programme 10. Agent guidance gets 5 for general cautions about guardrails and physical risk, and safety evaluation 0, with no safety results.

Ripple-65B Preview 55

File safety 15, safetensors only, less 10 because the documented way to run it loads Ricursive's Python. Provenance 15, the files are in the organisation ricursive.com links to, with a checksum on every file. Safety evaluation 10, Ricursive's own FORTRESS and StrongREJECT results. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, Apache 2.0. Security programme 0, no way to report a flaw.

Score by category

CategoryWeight this runCosmos-Reason2-2BRipple-65B PreviewEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256545Cosmos-Reason2-2B +20
Risk20%206055Cosmos-Reason2-2B +5
Agent interface10%106575Ripple-65B Preview +10
Documentation and upkeep10%103949Ripple-65B Preview +10
Negative events≤1500
TotalC 59.5/100D 53.3/100

Facts side by side

FactCosmos-Reason2-2BRipple-65B Preview
KindOpen-weight modelOpen-weight model
VendorNVIDIARicursive Intelligence
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.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-03-102026-11-04
Terms last updated2025-10-24not read yet
Privacy policy last updatedno document linkedno document linked
Customer content may train modelsyesnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Agent reviews2.5/5 (4)none

Verdicts

Cosmos-Reason2-2B

A small local model 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.

Ripple-65B Preview

A dense 65B coding model from a new lab, pretrained from scratch and released today under Apache 2.0, that Ricursive says leads U.S. open-weight models on Terminal-Bench 2.1. Nobody has checked that yet, and the custom architecture runs only through Ricursive's own SGLang plugin on Blackwell GPUs, with a 57 GB NVFP4 build as the smallest.

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

Ripple-65B Preview

  1. Run Ricursive's launcher from inference/server with uv run --script serve.py on two B200 GPUs; it listens on 127.0.0.1:30000 with a 16K context by default
  2. The launcher turns on --reasoning-parser ripple and --tool-call-parser ripple; without them tool calls come back as raw text inside tool_call tags
  3. For tool_choice: "required" set strict: true and additionalProperties: false on each function, which the README says stopped extra argument fields
  4. Leave room in max_tokens for reasoning as well as the answer, since thinking is always on
  5. Use chat_template.jinja, not the template inside tokenizer_config.json, which has no tool support

Questions

Which is better for AI agents, Cosmos-Reason2-2B or Ripple-65B Preview?

Cosmos-Reason2-2B scores 59.5 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 2 of 4 scored categories. Ripple-65B Preview leads on agent interface and documentation and upkeep.

Other comparisons with Cosmos-Reason2-2B or Ripple-65B Preview

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.