The robot you print is the robot you simulate.
One codebase for the parts, the MuJoCo model and the robot on the bench. Change a link and the simulation, the masses and the joint checks follow; train on the model, play the policy on the twin, then on the robot.
No export step to go stale.
The code that makes the parts also makes the simulation, so the robot that walks in MuJoCo has the masses, joints and limits of the one you print.
Joints from how the parts move, masses and inertia from the printed solids, collision shapes, rebuilt when the code changes.
A gait or a learned policy, on rough ground, slopes and steps, steered from the keyboard in the app.
MJX for training on the GPU and URDF, from the same code. Training runs go through a GPU queue in the background.
Built over weeks, by a person and an agent.
Their numbers are from today's model, failed checks included: KLIV's hips are being redesigned as this is written.
From the twin to the real robot.
The robot's description ties your software to the CAD, so the same joint order runs the simulation, the twin in the app and the servos.
The joint vector
robot.json lays your software's joint order on the CAD's joints, checked against the firmware's tables and locked in versions.
Live twin
The robot connected and polled, its pose on the model. It moves only once you arm it, and stops at once.
Datasets
LeRobot datasets replayed on the CAD, bad episodes marked, live recordings from the twin.
Training runs
Your own RL or imitation pipelines, started in the background, with metrics, evaluations and stale runs flagged when the model changes.
Servo identification
Time constant, speed, dead band and delay from a step test, back into the simulation.
Deploy
A policy exported and pushed to the robot's computer, started and benched, with what runs where.
Design, Motion and Simulate on one model.
Motion scripts are checked frame by frame for collisions, joints past their limits or speed, and feet that slide. The agent films them with one call.
Actuators, grippers and machines.
Smaller runs: the agent got one paragraph and built the mechanism with its checks.
Four of the runs.
See all the examplesThe tools a robot lab reaches for.
The tools from the whole package that matter for a robot. Tap one to read what it does.
Bearings, shafts and bolts to a standard, PDM and CE: see Professional.
Build your next robot with an agent.
We work first with a few labs and teams that build robots. Join the list and we will write when there is a build to try.