File size: 7,296 Bytes
09ddc2a 66c098a 09ddc2a 15f591d | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 | ---
library_name: transformers
tags:
- molmoact2
- robotics
- image-text-to-text
- libero
---
<img src="assets/MolmoAct2.svg" alt="MolmoAct Logo" style="width: auto; height: 50px;">
# **MolmoAct2-LIBERO**
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 checkpoint is fine-tuned on the full LIBERO training mixture, combining Spatial, Object, Goal, and Long suites. It is intended for both further fine-tuning and LIBERO policy inference.
## Quick Links
- 📂 Models: [Models](https://huggingface.co/collections/allenai/molmoact2-models), [Finetuned Models](https://huggingface.co/collections/allenai/molmoact2-finetuned-models)
- 📂 Datasets: [MolmoAct2-BimanualYAM Dataset](https://huggingface.co/collections/allenai/molmoact2-datasets), [MolmoAct2 Datasets](https://huggingface.co/collections/allenai/molmoact2-datasets), [Molmo2-ER Datasets](https://huggingface.co/collections/allenai/molmo2-er-datasets)
- 📄 Paper:
- 💻 Code: [allenai/molmoact2](https://github.com/allenai/molmoact2)
- 🎥 Blog Post: [MolmoAct2](https://allenai.org/blog/molmoact2)
## Intended Use
Use this checkpoint for LIBERO inference or for further fine-tuning. Dataset normalization metadata is stored in `norm_stats.json`; pass `norm_tag="libero"` at inference time.
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.
## Install
```bash
pip install torch transformers pillow numpy huggingface_hub
```
## Sample Input
This sample comes from `libero_10`, episode 0, frame 0. The LIBERO camera order is front/agent view followed by wrist view.
| Agentview RGB | Wrist RGB |
| --- | --- |
|  |  |
```python
from huggingface_hub import hf_hub_download
from PIL import Image
import numpy as np
repo_id = "allenai/MolmoAct2-LIBERO"
agentview_rgb = Image.open(
hf_hub_download(repo_id, "assets/sample_agentview_rgb.png")
).convert("RGB")
wrist_rgb = Image.open(
hf_hub_download(repo_id, "assets/sample_wrist_rgb.png")
).convert("RGB")
task = "put the white mug on the left plate and put the yellow and white mug on the right plate"
robot_state = np.array(
[
-0.05338004603981972,
0.007029631175100803,
0.6783280968666077,
3.1407692432403564,
0.0017593271331861615,
-0.08994418382644653,
0.03878866136074066,
-0.03878721222281456,
],
dtype=np.float32,
)
```
## Continuous Actions
```python
import numpy as np
import torch
from huggingface_hub import hf_hub_download
from PIL import Image
from transformers import AutoModelForImageTextToText, AutoProcessor
repo_id = "allenai/MolmoAct2-LIBERO"
agentview_rgb = Image.open(
hf_hub_download(repo_id, "assets/sample_agentview_rgb.png")
).convert("RGB")
wrist_rgb = Image.open(
hf_hub_download(repo_id, "assets/sample_wrist_rgb.png")
).convert("RGB")
task = "put the white mug on the left plate and put the yellow and white mug on the right plate"
robot_state = np.array(
[
-0.05338004603981972,
0.007029631175100803,
0.6783280968666077,
3.1407692432403564,
0.0017593271331861615,
-0.08994418382644653,
0.03878866136074066,
-0.03878721222281456,
],
dtype=np.float32,
)
processor = AutoProcessor.from_pretrained(repo_id, trust_remote_code=True)
model = AutoModelForImageTextToText.from_pretrained(
repo_id,
trust_remote_code=True,
torch_dtype=torch.float32,
).to("cuda").eval()
out = model.predict_action(
processor=processor,
images=[agentview_rgb, wrist_rgb],
task=task,
state=robot_state,
norm_tag="libero",
action_mode="continuous",
enable_depth_reasoning=False,
num_steps=10,
normalize_language=True,
enable_cuda_graph=True,
)
actions = out.actions
```
`images` should preserve camera order, for example `[agentview_rgb, wrist_rgb]`. Images may be PIL images or RGB arrays. `state` is the raw robot state, and 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 Actions
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.
```python
action_tokenizer = AutoProcessor.from_pretrained(
"allenai/MolmoAct2-FAST-Tokenizer",
trust_remote_code=True,
)
out = model.predict_action(
processor=processor,
images=[agentview_rgb, wrist_rgb],
task=task,
state=robot_state,
norm_tag="libero",
action_mode="discrete",
action_tokenizer=action_tokenizer,
enable_depth_reasoning=False,
)
```
## Model and Hardware Safety
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.
## Citation
```bibtex
@misc{fang2026molmoact2actionreasoningmodels,
title={MolmoAct2: Action Reasoning Models for Real-world Deployment},
author={Haoquan Fang and Jiafei Duan and Donovan Clay and Sam Wang and Shuo Liu and Weikai Huang and Xiang Fan and Wei-Chuan Tsai and Shirui Chen and Yi Ru Wang and Shanli Xing and Jaemin Cho and Jae Sung Park and Ainaz Eftekhar and Peter Sushko and Karen Farley and Angad Wadhwa and Cole Harrison and Winson Han and Ying-Chun Lee and Eli VanderBilt and Rose Hendrix and Suveen Ellawela and Lucas Ngoo and Joyce Chai and Zhongzheng Ren and Ali Farhadi and Dieter Fox and Ranjay Krishna},
year={2026},
eprint={2605.02881},
archivePrefix={arXiv},
primaryClass={cs.RO},
url={https://arxiv.org/abs/2605.02881},
}
```
|