Robots · Humanoids

Boston Dynamics Atlas teleoperation: from the VR rig to the Large Behavior Model

Boston Dynamics has published how it turns VR demonstrations into Atlas policies, step by step. It is one of the best public descriptions of a humanoid data pipeline, and a clear look at the operators behind it.

Boston Dynamics Atlas, Electric industrial humanoid
AI-generated illustration of the Boston Dynamics Atlas. For product photos, see Boston Dynamics.
Height and weight
1.9 m, 90 kg
Degrees of freedom
56, with fully rotational joints
Reach
2.3 m
Payload
50 kg instant, 30 kg sustained
Battery
4 h; swaps its own battery at a station
Protection and temperature
IP67; -20 to 40 °C
Control modes
Autonomous, teleoperated or tablet steering
Fleet software
Orbit (MES and WMS integration)

Updated

The electric Atlas is Boston Dynamics' production humanoid: 1.9 m tall, 90 kg, 56 degrees of freedom and a 50 kg instant lift, unveiled as a product at CES in January 2026. It is also the humanoid whose maker has been most open about how operators teach it. Boston Dynamics and Toyota Research Institute have described the VR rig, the data pipeline and the policy architecture in detail, and the head of the Atlas program has talked publicly about who the operators are and how long they take to train. That makes Atlas the best case study there is for anyone setting up humanoid teleoperation, even though very few people can buy one yet.

Can you buy an Atlas?

Not in 2026. In its CES 2026 announcement, Boston Dynamics said production was starting at its Boston headquarters, that "All Atlas deployments are already fully committed for 2026" to Hyundai's Robotics Metaplant Application Center and Google DeepMind, and that it plans to add customers in early 2027. The product page describes the current phase as early adoption with "a select number of early adopters". There is no published price and no public Atlas SDK. If you need a humanoid with operators on it before 2027, skip to the alternatives below.

Three ways to drive Atlas

Boston Dynamics says the product Atlas "can be controlled in three different ways: autonomous mode, teleoperated, or by using a tablet steering interface". Each one has a different job in a deployment:

Autonomous

Learned policies run the task. Boston Dynamics says a skill learned by one Atlas can be deployed across the fleet, with Orbit connecting the robots to MES, WMS and other plant systems.

Teleoperated

A person in VR drives the robot one-to-one. This is how demonstrations are collected and how a stuck task can be finished.

Tablet steering

Boston Dynamics has published little beyond the name, but it gives staff a way to steer the robot without putting on a VR rig, the kind of control a floor supervisor needs to move a robot out of an aisle.

The VR teleoperation rig, step by step

Boston Dynamics and TRI described the rig in their post on Large Behavior Models and Atlas. It sits on top of Atlas' model predictive controller, the same balance and whole-body control layer the robot uses on its own, through a custom VR interface:

Standing upper-body version

The first version used a headset, base stations, hand controllers and one chest tracker, with Atlas standing still. Mapping is one to one: a 1 cm hand movement moves the robot's hand 1 cm.

Whole-body version

Two more trackers on the operator's feet added one-to-one tracking of stance, support polygon and stepping, so the operator can walk the robot through loco-manipulation tasks while MPC keeps it balanced.

Same view as the policy

The operator sees what the policy will see: stereoscopic video, robot state, control targets, sensor readings and tactile feedback in a heads-up display, with haptic feedback through the controllers.

The "same information as the policy" rule is the most transferable idea here. If the operator relies on a cue the policy cannot see, such as a side view of the table, the policy learns actions with no visible cause. Show the operator the robot's own camera streams, not a better view.

From demonstrations to a Large Behavior Model

The published pipeline has four stages: collect teleop data on real hardware and in simulation; process, annotate and curate it, with quality-assurance tooling to review, filter and give feedback on episodes; train; and evaluate. The team wrote that "high quality demonstrations were a critical part of getting successful policies".

Model

A 450M-parameter diffusion transformer trained with a flow-matching objective, building on TRI's LBM work.

Inputs

Head-camera images at 30 Hz, proprioception and a language prompt.

Outputs

An action chunk of 48 steps (1.6 seconds), of which 24 are executed per inference, covering gripper joints, neck yaw, torso pose, hand poses and foot poses.

Recovery data

The team retrained policies with recovery demonstrations, episodes that show how to get out of a mistake, and says that is what let the policies react intelligently instead of only replaying the nominal path.

Faster than the operator

Policies could run 1.5 to 2 times faster than the demonstrations without significant loss in performance.

One caveat on hardware: the research Atlas in that post is listed at 50 degrees of freedom with 7-DoF grippers, while the CES product Atlas is listed at 56. Policies and datasets are tied to the body they were recorded on.

Who the operators are

In a September 2025 IEEE Spectrum interview, Atlas lead Scott Kuindersma gave the clearest description any humanoid maker has offered of its operator team: "The people doing it now are not roboticists; we have a team of 'robot teachers' who are hired for this." He said novice operators are "probably not generating the highest-quality motions for training policies", and that consistently producing good data over several hours "typically takes a couple of weeks of onboarding".

He also placed teleoperation at the top of the data pyramid, "the highest quality, hardest-to-get data", stressed the importance of a large baseline of actual on-robot data, said co-training with simulation had improved real-robot performance, and admitted that "no one knows the exact distribution" of the right mix. Those points are the planning assumptions for any humanoid data program: hire for physical skill and consistency rather than robotics degrees, budget weeks of onboarding per operator, and treat on-robot teleop as the scarce, expensive layer. Our humanoid teleoperator careers page describes the role from the operator side.

What a good operator does on an Atlas-style rig

Moves for the policy, not for the camera

Smooth, direct reaches and no hesitation mid-grasp. The policy will copy pauses and hunting motions, and with action chunks of 1.6 seconds a bad half-second ends up baked into every chunk.

Steps deliberately

With foot trackers mapped one to one, the operator's stance becomes the robot's support polygon. Shuffling, crossing feet or leaning on a desk all turn into robot behavior.

Records recoveries on purpose

A protocol that includes planned recoveries (regrasp a slipped part, re-step after a bad foot placement) gives the policy the episodes Boston Dynamics credits for robustness.

Uses only the robot's view

Headset video from the robot's cameras, not a better angle from the room. Anything the operator sees that the policy cannot becomes an action with no visible cause.

Stops before fatigue shows

VR with trackers is physical work. Short blocks with breaks keep the motion quality the onboarding weeks were spent building, and quality review catches drift between sessions.

Where TRI's LBM paper fits

People often cite TRI's Large Behavior Model study as Atlas research. It is related but not the same: the paper trains on almost 1,700 hours of data, including 468 hours of bimanual real-robot teleoperation, 45 hours of simulation teleoperation, 32 hours of UMI data and about 1,150 hours curated from Open X-Embodiment, and evaluates on bimanual Franka FR3 stations, not Atlas. Its headline result, that pretrained LBMs can learn new tasks with 3 to 5 times less data in challenging settings, is the reason the Atlas team adopted the approach. It also found that data normalization choices often mattered more than architecture changes, a reminder that consistent, well-formatted episodes are worth as much as clever models. Our teleoperation data collection guide covers how to keep episodes consistent from the first one.

Control loop and latency for a remote Atlas operator

Because the VR rig drives targets into MPC rather than raw joint commands, the controller on the robot keeps a 90 kg machine balanced even when the operator's signal arrives late or jittery. That is what makes remote operation of a robot this size plausible at all. The remaining question is task precision. Tire handling and bin moves tolerate a few hundred milliseconds of delay; tight assembly and threading do not, and need an operator close to the robot or a policy doing the fine part with the human supervising. Our teleoperation latency guide breaks budgets down by task.

What happens to Atlas in 2026

The 2026 fleet goes to two places. Hyundai's application center is the industrial test bed, and Hyundai Motor Group said at CES that it is preparing to deploy tens of thousands of Boston Dynamics robots in its facilities, with Hyundai Mobis supplying Atlas actuators. The Google DeepMind partnership will combine DeepMind's Gemini Robotics models with Atlas for industrial tasks, starting with automotive, with joint research due to begin in 2026. Neither announcement says anything about outside data access, so expect no public Atlas datasets in the near term.

If you need humanoid operators before 2027

Teams that want to reproduce the Atlas recipe now (VR teleop, recovery demonstrations, a diffusion or flow-matching policy) usually do it on a buyable research humanoid. The full-size Unitree H2 is the nearest in stature and was added to Unitree's open xr_teleoperate stack in v1.6, which records episodes directly. The smaller Unitree G1 has the largest open teleop and dataset ecosystem of any humanoid.

How RoboPilots supplies robot teachers

Kuindersma's description of the job is close to what we staff. Several humanoid makers have sent RoboPilots robots to test our operating protocols. On a customer program we train a dedicated group of operators on your own unit and task protocol, including recovery demonstrations, so the weeks of onboarding happen once and the same people stay on your robot.

One-week trial

Sets the clean-episodes-per-operator-hour baseline on your robot before a longer statement of work.

Coverage

Shifts across time zones, including US Pacific, so the robot collects or stays supervised around the clock.

Data

Episodes reviewed, labeled by task and outcome and delivered as LeRobot, RLDS or HDF5.

Interfaces, specs and sources

  • VR teleop on BD's MPC controller
  • Tablet steering interface
  • Autonomous mode (LBM policies)
  • Orbit fleet software
  • No public Atlas SDK

Availability: Not available to new buyers yet. Boston Dynamics said at CES on January 5, 2026 that all Atlas deployments for 2026 are fully committed, to Hyundai's RMAC and Google DeepMind, and that it plans to add customers in early 2027. No price is published.

Specs are the maker's published figures, checked on . RoboPilots is not affiliated with Boston Dynamics; product names are trademarks of their owners.

Frequently asked questions

Can you buy a Boston Dynamics Atlas?
Not yet. Boston Dynamics says all 2026 Atlas deployments are committed to Hyundai and Google DeepMind and that it plans to add customers in early 2027.
How much does Atlas cost?
Boston Dynamics has not published a price for Atlas. Pricing figures circulating online are third-party estimates, not list prices.
Is Atlas teleoperated or autonomous?
Both. Boston Dynamics says Atlas can run in autonomous mode, be teleoperated, or be steered from a tablet. Its autonomous policies are trained on VR teleoperation demonstrations.
How is Atlas teleoperated in VR?
An operator wears a VR headset with hand controllers and trackers on the chest and feet, mapped one to one onto the robot, while Atlas's model predictive controller keeps it balanced. The operator sees the same camera and sensor information the policy uses.
What is the Atlas Large Behavior Model?
A 450M-parameter diffusion transformer policy, built with Toyota Research Institute, that takes camera images, proprioception and a language prompt and outputs 1.6-second chunks of whole-body actions.