MolmoAct2 is an open vision-language-action model for robot control. It builds on Molmo2-ER and attaches a flow-matching continuous action expert that conditions on the VLM key-value cache through a per-layer connection.

This 90K-step checkpoint is fine-tuned on the RoboDojo training set with absolute joint-pose control and language instructions. It is intended for both further fine-tuning and dual-arm RoboDojo policy inference.

Use this checkpoint for dual ARX X5 inference in RoboDojo or for further fine-tuning. Dataset normalization metadata is stored in norm_stats.json. Pass norm_tag="robodojo" at inference time. The model predicts 25-step, 14D absolute joint-pose action chunks.

Continuous action prediction is the intended and recommended inference mode. Discrete action prediction is exposed for parity and debugging, but we use continuous actions by default.

This sample comes from the RoboDojo training dataset RoboDojo_lerobot_v30_video, episode 0, frame 0. The camera order for this checkpoint is high, left wrist, right wrist.

MolmoAct2 was trained with mixed precision. For the RoboDojo evaluation, we ran inference in bfloat16. The float32 path uses the most GPU memory: roughly 26GB with CUDA graph enabled, or around 24GB without CUDA graph.

If you have a GPU with less memory, you can run inference with bfloat16 instead:

Using bfloat16 is much more memory efficient and can run under 16GB of GPU memory in our tests. It usually does not hurt performance much.

images should preserve camera order: [top_rgb, left_rgb, right_rgb], corresponding to high, left-wrist, and right-wrist cameras. Images may be PIL images or RGB arrays. state is the raw 14D robot state, and absolute 14D actions are returned in robot scale.

normalize_language=True is the default. It lowercases the task string and removes trailing sentence punctuation to match training preprocessing. Set it to False if you need to preserve the task text exactly.

enable_cuda_graph=True is the default. The first few calls can be slow because the model warms up and captures CUDA graphs. run several random warm-up calls before measuring deployment latency. num_steps controls the continuous flow solver and defaults to the checkpoint config value, 10.

Depth reasoning is disabled for this checkpoint. Calling enable_depth_reasoning=True will raise an error.

Discrete action inference requires a caller-provided action tokenizer. It is not saved in this repository. Discrete mode decodes action tokens directly. the continuous action expert is not used.

MolmoAct2 generate robot actions from visual observations and language instructions, but their behavior may vary across embodiments, environments, and hardware configurations. Users should carefully validate model outputs before deployment, especially when operating physical robots or other actuated systems. Where possible, actions should be monitored through interpretable intermediate outputs (adaptive depth map), simulation rollouts, action limits, or other safety checks before execution on hardware. The model’s action space should be bounded by the training data, robot controller limits, and task-specific safety constraints, including limits on speed, workspace, torque, and contact force. Users should follow the hardware manufacturer’s safety guidelines, use appropriate emergency-stop mechanisms, and operate the system only in a safely configured environment with human supervision.