MuJoCo Playground
MuJoCo Playground is a suite of robot environments, reinforcement learning tasks, and hardware workflows written in PyTorch and built on reaf-sim, MuJoCo, and MuJoCo Warp.
Robots exist in mujoco_playground/robots/, either in simulation or paired with a hardware counterpart, enabling end-to-end workflows across simulation and hardware:
- Large-batch RL training on GPU: with state and vision observations across control, manipulation, and humanoid whole-body tracking.
- Sim & real teleoperation: with leader-follower control and episodic MCAP logging.
- System identification: fitting simulated joint dynamics to logged hardware trajectories via
mujoco.sysid. - Zero-shot sim-to-real policy deployment: running the same task layer and policy in simulation (
--mode=sim) and on hardware (--mode=real). - Agentic manipulation: for vision-language model (VLM) examples across simulation and hardware (
SO-101,i2rt YAM).
|
Whole body motion tracking |
Sim teleoperation |
|
Real teleoperation |
System identification |
|
Sim2Real and interactive viewer |
Agentic manipulation |
Installation
Clone the repository and sync dependencies with uv:
git clone https://github.com/google-deepmind/mujoco_playground.git && cd mujoco_playground
# Then install with one of:
make sync # For GPU, good for RL training
make sync-cu12 # For CUDA 12 on Linux
make sync-cpu # Or for CPU only, (i.e. on macOS)
Verify your installation by running the test suite:
make test
Getting Started
To get started, either try training an RL policy, or try agentic manipulation in simulation or on the real hardware.
Train & Visualize an RL Policy
Train a PPO policy across parallel GPU environments with RSL-RL:
# Train SO-101 Pick-Cube
uv run --extra rl python -m mujoco_playground.rl.rsl_rl.train \
--env=SO101PickCubeVision \
--logdir=/tmp/rslrl_logs/so101_pick_cube_vision
# --overrides='{"nworld": 64}' # For CPU
# Play back the trained policy in the interactive viewer
uv run --extra rl python -m mujoco_playground.rl.rsl_rl.play \
--env=SO101PickCubeVision \
--resume_path=/tmp/rslrl_logs/so101_pick_cube_vision
Monitor training curves in TensorBoard:
uv run --extra rl tensorboard --logdir=/tmp/rslrl_logs/so101_pick_cube_vision
Optionally set up the SO-101 hardware and deploy to the real arm:
# Deploy the trained policy on the physical SO-101 follower arm
uv run --extra so101 --extra rl python -m \
mujoco_playground.tasks.manipulation.pick_cube.so101.deploy.run \
--mode=real \
--checkpoint=/tmp/rslrl_logs/so101_pick_cube_vision
Try Agentic Manipulation
Spin up the agentic tabletop manipulation task directly from your coding agent with a prompt in sim or real:
Start the tabletop_v0 bridge for the yam in sim and get it to <your task>,
following mujoco_playground/tasks/agentic/tabletop_v0/AGENT_PROMPT.md
Swap sim for real to run on hardware, or so101 for yam (see AGENT_PROMPT.md).
Documentation & Contributing
- Documentation: See the MuJoCo Playground documentation.
- Contributing: See the contributing guide for contribution guidelines.
- Changelog: See the changelog.
Citation
If you use MuJoCo Playground in your work, please cite it as follows (see the GitHub contributors page for the full list of contributors):
@software{mujoco_playground_2026,
author = {Tabanpour, Baruch and Howell, Taylor and Haves, Sam and Abeyruwan, Saminda and Ma, Tony and Suh, Dan and {MuJoCo Playground Contributors}},
title = {{MuJoCo Playground}},
url = {https://github.com/google-deepmind/mujoco_playground},
year = {2026},
}
For the RSS 2025 benchmark suite that was built on JAX/MJX (see rss2025), please cite:
@misc{mujoco_playground_2025,
title = {MuJoCo Playground: An open-source framework for GPU-accelerated robot learning and sim-to-real transfer.},
author = {Zakka, Kevin and Tabanpour, Baruch and Liao, Qiayuan and Haiderbhai, Mustafa and Holt, Samuel and Luo, Jing Yuan and Allshire, Arthur and Frey, Erik and Sreenath, Koushil and Kahrs, Lueder A. and Sferrazza, Carlo and Tassa, Yuval and Abbeel, Pieter},
year = {2025},
publisher = {GitHub},
url = {https://github.com/google-deepmind/mujoco_playground}
}
License & Disclaimer
All content in this repository is licensed under the Apache License, Version 2.0. See LICENSE for details.
This is not an officially supported Google product.
Metadata
Release files for playground 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| playground-1.0.1.tar.gz | 16.9 MB | Without provenance | Details for playground-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| playground-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for playground-1.0.1-py3-none-any.whl |
Total release size: 17.5 MB
Release files / playground-1.0.1.tar.gz
| Download URL | playground-1.0.1.tar.gz |
|---|---|
| Size | 16.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b0811a2b378e6d1d4e6d3b0bf80b3cedb815fd6ceb05aab2048505767d5c0af
|
|
BLAKE2b-256 checksum How to use checksums |
8ee89da247c144efed738652e06696bfd31447ff057d684f6767233ee5e1e41c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / playground-1.0.1-py3-none-any.whl
| Download URL | playground-1.0.1-py3-none-any.whl |
|---|---|
| Size | 619.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
25c70efa23ecf5f1cc2f008b84e684f3e496a18725a0a290f5b7a73a516bb266
|
|
BLAKE2b-256 checksum How to use checksums |
5f2016c20bf0022f71668a98add432bbc537f2065e87d5796baa6e1857974ecf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for playground 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.