NVIDIA Cosmos-H-Dreams: Real-Time Open Surgical Simulator

NVIDIA's Cosmos-H-Dreams runs at 160 fps on one RTX PRO 6000, with weights, code, dataset, and recipe open. Not a robot controller, NVIDIA warns.

A laboratory pipette filling a tray of clear sample wells, used to illustrate a computer science research release.
Photo via Unsplash

On July 27, 2026, NVIDIA released a real-time, action-conditioned surgical simulator that runs from a single workstation GPU. It ships with the open weights, training code, a self-forcing distillation tutorial, and the underlying dataset. It is also, by the company’s own repeated disclaimer, “a research and development platform, not a diagnostic system, a replacement for intraoperative imaging, or a controller for a physical surgical robot.” The release sits next to recent work on autonomous surgical robots trained on surgeon video, and adds another NVIDIA open release to the same track as Nemotron 3 on Hugging Face.

That clause is the most important sentence in the Hugging Face release post, and it is the one readers should remember before drawing any clinical conclusion from the launch.

What Cosmos-H-Dreams actually does

Cosmos-H-Dreams is a “real-time, action-conditioned generative simulator for surgical robotics” derived from NVIDIA’s Cosmos-Predict2.5-2B backbone, a 2-billion-parameter diffusion transformer. It takes an initial RGB frame plus a live robot kinematics stream and autoregressively generates future surgical video frames. The released checkpoint is specialized for the da Vinci Research Kit (dVRK) tabletop suturing setup, with a 20-dimensional dual-arm action vector zero-padded to 44 dimensions, and the post describes integration work with CMR Surgical and Cambridge Consultants to run on the Versius platform.

The headline number is throughput. According to the release post, the distilled student model runs at about 160 frames per second on a single NVIDIA RTX PRO 6000, compared to roughly 10 fps for the teacher model it was distilled from. The team gets there with a three-stage recipe: a “surgical teacher” fine-tuned on the JHU dVRK tabletop mixture (which includes both successes and failures like needle drops and missed throws, so the simulator reproduces the consequences of poor actions), a “causal warmup” of the student, and a “self-forcing distillation” stage that lets the student roll forward on its own outputs while matching the teacher’s distribution. The distillation step cites the self-forcing line of work (arXiv:2506.08009).

The training pipeline is therefore the interesting story, not the model size. The base model is 2B parameters, but the value is in the recipe: the post gives a concrete starting horizon of 12 frames and progressively extends to 72 frames, then uses a streaming KV cache, CUDA-graph capture, and a LightTAE decoder under the FlashDreams inference engine to push the throughput.

What NVIDIA released and where you can run it

The release is unusually open by NVIDIA’s standards. The full inventory of assets, all linked from the release post:

  • Student model: huggingface.co/nvidia/Cosmos-H-Dreams under the NVIDIA Open Model License Agreement
  • Teacher model: huggingface.co/nvidia/Cosmos-H-Surgical-Simulator
  • Code: github.com/isaac-for-healthcare/Cosmos-H-Dreams
  • Inference engine: github.com/NVIDIA/flashdreams
  • Teacher training and self-forcing tutorial: github.com/NVIDIA-Medtech/Cosmos-H-Surgical-Simulator/blob/main/docs/tutorial_teacher_training_and_self_forcing.md
  • Dataset: huggingface.co/datasets/nvidia/PhysicalAI-Robotics-Open-H-Embodiment

The hardware target is the workstation tier. The model card lists NVIDIA Ampere, Blackwell, Hopper, and Lovelace generations, with testing on a single RTX PRO 6000 and runs reported on A100 and H100. That is a meaningful but not exotic compute budget for a research lab, and it sits in the same envelope the site has been tracking for consumer local-AI work. The model card adds that the input expects a 10 Hz effective kinematic rate for dVRK and recommends a 288 by 512 resolution; the output streams 12-frame blocks autoregressively with a bounded-memory KV cache.

NVIDIA also published two client surfaces. A browser client accepts keyboard commands over WebRTC, and a Meta Quest client uses WebXR with controller motion mapped into robot actions. The closed-loop integration is where the simulator stops being a video generator and becomes a place where a learned policy like GR00T-H can be evaluated. Real-time generative simulation, the post argues, can become “an active partner in surgical policy development” by generating rare failures on demand and providing scalable environments for imitation or reinforcement learning.

The caveats are also written into the model card. The card says the model will not blur people or preserve the proportions of subjects, that failure and out-of-distribution episodes were intentionally retained in training so the simulator renders consequences of poor actions, and that “developers are responsible for proper rights and permissions on input content.” The release date for the GitHub and Hugging Face assets is July 23, 2026, with the public blog post on July 27.

What This Means

For AI builders, the release is a working counterexample to the claim that you need a frontier datacenter to ship a fine-tuned world model. The 2B-parameter footprint and the self-forcing distillation recipe are within reach of a research lab with one or two RTX PRO 6000 cards, and the teacher-training tutorial is the kind of artifact that tends to outlast the headline model. The pattern is familiar from the open-weight LLM cycle: NVIDIA releases the base, the recipe, and the dataset, and downstream groups retarget the same recipe to other surgical platforms, other robot kinematics, or other domains entirely.

For clinicians and patient-facing readers, the practical message is to look for how a deployment is wired, not at the demo. The same post that calls the simulator “an interactive environment that a person or a learned policy can control in a closed loop” also explicitly disclaims diagnostic, imaging, and controller roles. The dVRK tabletop suturing checkpoint is a research artifact, not a clinical tool.

For the open-weights debate, the launch is one more data point in a year of open-edge releases. The site has already tracked Nvidia’s Cosmos-3-Edge on Hugging Face and the broader Cosmos platform; a real-time surgical simulator extends that footprint into a regulated domain. The combination of an open license, an open dataset, and an open adaptation recipe is rare in surgical robotics, and it shifts the burden of any safety boundary to the developer integrating the model. For more on what is in the site’s open-weight and local-AI coverage, see the local-AI hub.

The Bottom Line

Cosmos-H-Dreams is a 2B-parameter surgical simulator that runs at about 160 fps on a single RTX PRO 6000, ships with its weights, code, dataset, and recipe, and is licensed for research. It is a real tool for training and evaluating surgical policies. It is not, by NVIDIA’s own writing, something you should hand to a patient or a real robot.