I made my humanoid walk in my virtual kitchen using a pretrained walking policy.
Getting to my stove should not be this hard.
My kitchen, recreated in MuJoCo. Walking policy from Lucky Robots’ G1 Manipulation Challenge.
I put TypeSafe’s JEV in control of G1 humanoid in my virtual kitchen.
The mission: reach the stove with obstacles on the way.
A VLM and depth information helped map the kitchen.
A path planner produced possible ways around the obstacles, and JEV chose which move to make next.
A pretrained walking policy handled locomotion, with calibrated controls for turns, forward movement, and curves.
The robot reached the stove in about 64 seconds of simulation time. This video shows the highlights.
Still a prototype, but pretty cool watching perception, decisions, and movement come together.
@0fir0z Qwen3.8 generates a scene description.
Then scene description plus potential trajectories is passed to JEV.
Finally JEV makes trajectory decision.
Trajectory runs a pretrained policy for locomotion.
The humanoid can now load a plate into the dishwasher in a physics simulation of my own kitchen.
Programmed arm motion, contact-based grasp, and an invisible support keeping the robot upright.
Balance is next.
Data is the real bottleneck.
Foundation models are improving at general tasks because those domains have abundant training data.
Using them for domain-specific workflows is inefficient by design.
They’re optimized for user satisfaction, not accuracy.
The next leap won’t come from larger models, but from allowing domain experts to curate better datasets, and contribute to foundation model training.