Cosmos-Reason2-2B vs DeepSeek-V3.2

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.

DeepSeek-V3.2

DeepSeek-V3.2 is an MIT-licensed reasoning model trained for parallel tool calls, with thinking chosen per request, for long agent work. It needs about 690 GB of FP8 files, eight 80 GB GPUs in vLLM's recipe and prompts built from DeepSeek's Python. The main risk is neglect, with no file changes since December 2025 and no safety evaluation.

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

DeepSeek-V3.2

1. Start it with vLLM's recipe, vllm serve deepseek-ai/DeepSeek-V3.2 --tensor-parallel-size 8 --tokenizer-mode deepseek_v32 --enable-auto-tool-choice --tool-call-parser deepseek_v32 --reasoning-parser deepseek_v3
2. It doesn't fit the 107.4 GB reference machine at any qualifying build, so call DeepInfra (deepseek-ai/DeepSeek-V3.2) or SambaNova (DeepSeek-V3.2) instead
3. Outside vLLM, build prompts with encoding/encoding_dsv32.py and wrap parse_message_from_completion_text in error handling, since DeepSeek says it handles well-formed output only
4. Pick thinking or chat with thinking_mode, and read the reasoning from reasoning_content
5. Send developer messages only for search-agent prompts, the only use DeepSeek gives that role
6. Use temperature 1.0 and top_p 0.95 and keep prompts within 128K tokens