Record. Clone. Reinforce. Control a simulated SO-101 with an SO-100 or SO-101 leader arm, record LeRobot demonstrations, train with behavior cloning, then fine-tune with reinforcement learning. One Python library connects the workflow.
Get started
With Python 3.12 or newer, install the library:
pip install so101-nexus
Run a simulated robot. No hardware is required:
import gymnasium as gym
import so101_nexus.mujoco # registers the MuJoCo environments
env = gym.make("MuJoCoPickLift-v1", render_mode="human")
obs, info = env.reset(seed=0)
env.action_space.seed(0)
for _ in range(1000):
obs, reward, terminated, truncated, info = env.step(env.action_space.sample())
if terminated or truncated:
obs, info = env.reset()
env.close()
See Installation for optional extras and source setup. The Quickstart explains the example and shows how to change objects.
To train without a local setup, open the BC + PPO Colab notebook. Select a GPU runtime and run all cells with the published demonstrations.
From demonstrations to policy
- Record demonstrations with a leader arm.
- Clone the demonstrations with behavior cloning.
- Reinforce the policy with GPU-parallel PPO.
Environments lists the tasks. Examples lists the scripts and notebooks. MuJoCo provides Gymnasium simulation and CPU batching. The optional Warp backend provides GPU batching. See Backends for requirements and physics differences.
This library is in beta. See Stability and versioning before you depend on an API.
Contribute
Follow the source installation guide, then run:
make format lint typecheck
make test
See CONTRIBUTING.md. Source code uses the Apache-2.0 License.
Metadata
Release files for so101-nexus 0.12.0
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 |
|---|---|---|---|---|
| so101_nexus-0.12.0.tar.gz | 16.8 MB | With provenance | Details for so101_nexus-0.12.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| so101_nexus-0.12.0-py3-none-any.whl | Python 3 | none | any | Details for so101_nexus-0.12.0-py3-none-any.whl |
Total release size: 29.9 MB
Release files / so101_nexus-0.12.0.tar.gz
| Download URL | so101_nexus-0.12.0.tar.gz |
|---|---|
| Size | 16.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aef83ba7d91420cce906731b5667541c1bd4f04035d8fd28c5b24229422e3455
|
|
BLAKE2b-256 checksum How to use checksums |
896f9468e16236e751777e8c3ea9a26387fc392b65ff160b090838fda126d021
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logRelease files / so101_nexus-0.12.0-py3-none-any.whl
| Download URL | so101_nexus-0.12.0-py3-none-any.whl |
|---|---|
| Size | 13.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
667cf0698124595edadcd589730fbf65db1915991c3e5e14da1eedb4c7a33722
|
|
BLAKE2b-256 checksum How to use checksums |
c0fdc98bf8c948dfb1dc66c37fd34dab75dab675678c6ba372c1d17fccf1e43d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logSecurity for so101-nexus 0.12.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for so101_nexus-0.12.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logA 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.