Phase 1: GDP-Grounded Simulation Selection
See the 25 simulations →Paid work
18,796 tasks valued by wages
Everyday life
valued by time spent
Scaling Physical Simulations with Digital Agents
Coding agents build realistic robotics simulations of real physical work. RoboWorld has 25 of them, from welding and drilling to pouring wine and folding laundry, and even the best frontier models fail every test task.
Videos recorded as evidence by the agents that built each simulation.
Our core insight is that creating a simulation is a coding agent task. Scenes, physics, tasks and rewards are all code, so as coding agents improve, the simulations they build improve too.
We break the tasks of 1,016 occupations and 465 everyday activities into 31,961 atomic physical actions, valued by wages or by time spent. An optimization selects 120 simulations that cover the most valuable physical work, and we build 25 of them.
A creation agent builds each simulation in code and must show evidence that it is good, such as renders, physical measurements and assisted demos. Four audit agents check it against ten criteria, and one of them tries to break it with legal robot actions. The creation agent fixes what they find, over three rounds.
A task creation agent proposes tasks of targeted difficulty. Six audit agents, one per criterion, check each task, including whether it is solvable and whether its reward is correct. Every task can run with different robots and under variations of the scene.
Frontier models improve across repeated attempts, and faster with privileged simulator state. That state also helps models that lack it: through a coach’s hints, through a model’s own privileged practice, and through code policies whose demonstrations train VLAs such as π0.5.
Hover over any part of the pipeline for details. Click a simulation to play it.Tap any part of the pipeline for details, and tap a simulation to play it.
18,796 tasks valued by wages
valued by time spent
lessons across simulations
researches the activity, builds scene, physics, and robot in code
VLAs, coding agents
proposes diverse tasks of targeted difficulty
p “Play ‘Hot Cross Buns’ on the xylophone with the mallets at 85 beats per minute.”
V scores the simulated sound: right notes, in time, and clean.
three attempts in one context
reset to the same start, keep notes and code
improves without weight updates, faster with privileged state
up to 10 qualitative hints, never numbers or commands
first-attempt reward: hints from privileged state double it
π0.5 success on two gift box tasks
Each simulation models the physics its work depends on, from liquids and cloth to soil, soft tissue, sound and molten metal. Click a card to enlarge it. Clips marked assisted had outside help, such as phantom hands, outside forces, supports or fixtures, as their recordings state.
Each simulation has eight tasks, from entry level to its hardest, which is its test task. Each task describes the job as one would describe it to a person, and a verifier scores it from the physical state of the simulation.
25 test tasks, one per simulation, and no model completes any of them. On an easier subset of 25 training tasks the best model succeeds 32% of the time, and success drops as the robot gains degrees of freedom.
| # | Model | Test Reward | Test Success | Easier Success | Arms | Mobile | Humanoid |
|---|---|---|---|---|---|---|---|
| 1 | Claude Opus 5.5 (xHigh) | 0.06 | 0% | 32% | 35% | 20% | 33% |
| 2 | GPT-6 Astra (xHigh) | 0.009 | 0% | 24% | 29% | 20% | 0% |
| 3 | GPT-6.1 Terra (xHigh) | 0.002 | 0% | 12% | 18% | 0% | 0% |
Reward is averaged over the 25 test tasks. It credits partial progress and is computed from the physical state of the simulation.
Arms, Mobile and Humanoid give success on the easier subset by robot: fixed-base FR3, Panda and UR10e arms (17 tasks, 8 to 16 DoF), the Mobile FR3 Duo (5 tasks, 20 DoF), and the Unitree G1 and H1-2 humanoids (3 tasks, 39 to 43 DoF).
Five ways a frontier model learns in RoboWorld, all with Claude Opus 5.5. The first four use 11 simulations, and code as policy uses two gift box tasks. Pick a setting to see what the model sees, what helps it, and how far it gets. Hover over the chart for exact values.Tap the chart for exact values.
Models often build their own tools to solve tasks, but they also overstate their success and even try to game the verifier. Each image is the camera image the model received or a render of a verified replay. Hover over a card for the full story, and click to enlarge.Tap a card to enlarge it and read the full story.
The robot plays a xylophone. Claude Opus 5.5 turned the simulated microphone into a sensor, using sound to detect when the mallet touched a bar and which note it played. When a note came out wrong, it worked out that the mallet had twisted in its gripper.
Its humanoid had fallen. GPT-6 Astra ran a pretrained get-up policy, and since the robot has no tilt sensor, it estimated the robot's tilt from the ceiling lines in this head camera image.
Claude Opus 5.5 had to kick a ball into a goal with a humanoid. It built its own simulation of the robot, found that the robot could not stay standing, and designed a kick that strikes the ball while the robot falls. It scored without ever seeing the goal.
GPT-6 Astra found the brake by reading the operator manual of a real Toyota forklift. In one attempt, it reported that the brake had stopped the forklift, while the truck had in fact reversed into the dock wall.
The fish frame must end up in a pan separate from the fillets. Claude Opus 5.5 expected the verifier to check only the frame, and placed the whole uncut fish in that pan, hoping for partial credit. The verifier measures the physical state, found the fillet meat in the pan, and gave no reward.
@misc{aggarwal2026gymanythingrobotics,
title={Gym-Anything for Robotics: Scaling physical simulations with digital agents},
author={Pranjal Aggarwal and Sean Welleck},
year={2026},
eprint={2610.40565},
archivePrefix={arXiv},
primaryClass={cs.RO},
url={https://arxiv.org/abs/2610.40565},
}