Motus2 README

The project's README from github.com/shengshu-ai/Motus2. As one markdown file: README.md.

Motus2: A Self-Evolving General World Model for Dexterous Manipulation

Project Page arXiv Hugging Face

Overview

General embodied agents should perceive, predict, act, evaluate, and improve within a unified system. World models have shown great promise in building such agents, yet existing models typically append an action output head to a world simulator, without coupling them into a closed decision-and-learning loop for policy improvement. We present Motus2, a self-evolving general world model for dexterous manipulation. Motus2 advances world modeling through model scaling and data scaling. For model scaling, a single model with shared weights exposes three control interfaces: a policy (world–action model), a simulator (action-conditioned world model), and an evaluator (value model). The policy proposes candidate action chunks, the simulator predicts their visual consequences, and the evaluator assesses the predicted outcomes. Their coupling forms a closed decision-and-learning loop for policy improvement. This formulation uses curated expert demonstrations for action learning, while failed and suboptimal interactions provide valuable evidence for dynamics modeling and value learning. For data scaling, Motus2 progresses from large-scale monocular egocentric data to synchronized stereo egocentric data, followed by robot-domain adaptation with robot trajectories and supplementary human–robot alignment data. Motus2 further studies global-autoregressive and hybrid-memory extensions of its sliding-window context, adds tactile feedback for contact-aware control, and is instantiated on a fully biomimetic platform with stereo vision, dual arms, dual dexterous hands, and tactile sensing. Together, egocentric data scaling and closed-loop general world model scaling provide a general path toward self-evolving dexterous manipulation.

Motus2 overview

Updates

Open-Source Roadmap

Citation

If you find Motus2 useful in your research, please cite:

@misc{bi2026motus2,
  title         = {Motus2: A Self-Evolving General World Model for Dexterous Manipulation},
  author        = {Hongzhe Bi and Zihao Zhou and Yihang Tang and Jingrui Pang and
                   Shuhe Huang and Haitian Liu and Runqing Wang and Shuai Huang and
                   Yichen Wang and Yiming Cheng and Ruowen Zhao and Zhenghua Li and
                   Hengkai Tan and Xiaolong Liu and Jinhui Wan and Jiabao Liu and
                   Min Zhao and Fan Bao and Jun Zhu},
  year          = {2026},
  eprint        = {2608.30237},
  archivePrefix = {arXiv},
  primaryClass  = {cs.RO},
  url           = {https://arxiv.org/abs/2608.30237}
}

Motus2 (shengshu-ai/Motus2)

Searching Database…

685 ·GitHub
What is this?Motus2 is a self-evolving general world model for dexterous robot manipulation. A single model with shared weights acts as a policy, a simulator, and an evaluator, coupling them into a closed decision-and-learning loop so the system can perceive, predict, act, and improve itself.
Is this a ready-to-use model, or more of a research framework?It's a research model/codebase, not a drop-in tool: a single model exposes three control interfaces (policy, simulator, evaluator) that work together, and it's meant to be scaled with large egocentric and robot data rather than used out of the box.
How do I get it running?You can't yet — no code or checkpoints are published. The authors plan to release pretraining checkpoints and training code (video pretraining, value/MBRL training, memory infrastructure, tactile code) progressively throughout September 2026.
What's the catch right now?Everything in the Open-Source Roadmap is unchecked — pretraining checkpoints, video pretraining code, value training code, MBRL code, memory infrastructure, and tactile code are all still pending release.
What do the policy, simulator, and evaluator interfaces actually do?The policy proposes candidate action chunks, the simulator predicts their visual consequences, and the evaluator assesses how good those predicted outcomes are, forming a closed decision-and-learning loop for improving the policy.
How does Motus2 scale its training data?It progresses from large-scale monocular egocentric video to synchronized stereo egocentric data, then adapts to robot trajectories plus supplementary human-robot alignment data for domain transfer.
Why is it called 'self-evolving'?Because failed and suboptimal interactions, not just curated expert demonstrations, feed back into dynamics and value learning, letting the model improve its own policy through the coupled simulator-evaluator loop rather than relying only on hand-labeled success data.
What hardware does Motus2 target?A fully biomimetic robot platform with stereo vision, dual arms, dual dexterous hands, and tactile sensing, with tactile feedback added for contact-aware control.
Size
<0.1 MB
Stars
685
Updated
CommitSep 11
Age
1mo
Commits · 90 Days