Let the Body Follow: Coupled Egocentric Control for Whole-Body Robot Teleoperation

A coupled egocentric control approach for whole-body robot teleoperation that coordinates body and limb movements from an egocentric perspective, submitted to Humanoids 2026.

What is Embodied AI 101?

Stay in the loop on research in AI and physical intelligence.

Let the Body Follow: Coupled Egocentric Control for Whole-Body Robot Teleoperation.

Teleoperation of humanoid robots aims to combine human intelligence and intent with the raw physical capabilities of a robot. As Darvish et al. note, teleoperating humanoids “enables the integration of the cognitive skills and domain expertise of humans with the physical capabilities of humanoid robots”. In practice this means a human operator can perform complex tasks—manipulating heavy objects, navigating cluttered spaces, or handling delicate tools—with the safety and endurance benefits that a robot body provides. The promise is enormous: imagine a technician controlling a life-sized robot on Mars or a rescue worker guiding a humanoid into a collapsed building. But delivering on that promise is deeply challenging. A full humanoid body can have 30–40 actuated degrees of freedom (DoF) or more, yet we expect a single human operator (often equipped only with a handful of controls) to effortlessly command it as if it were a natural extension of their own body.

One way to make teleoperation more natural is to enhance the operator’s sense of embodiment – the intuitive feeling that “this robot is an extension of me.” Recent studies have shown that when the teleoperation interface feels highly embodied and imposes minimal cognitive load, operators perform longer and produce higher-quality demonstration data for learning. For instance, Bianchi Moyen et al. found that a strong sense of embodiment in a mobile-manipulation interface substantially improves user experience and data quality, especially for long-horizon tasks. In other words, if the interface can make the operator feel as though they are actually in the robot’s body (and allow them to issue commands with little thought), complex tasks become easier and safer.

Despite decades of work, existing teleoperation interfaces still fall short of ideal embodiment and ease of control. Many systems decouple the operator’s joints and sensors from the robot’s resistors, forcing split modes or switching between control schemes. For example, a common approach is to let the operator use their arms (tracked with motion capture or controllers) to drive the robot’s arms, but then separately use a joystick or keyboard for locomotion and body orientation. This upper-body vs. lower-body split often leads to awkward coordination: the operator might look one way, reach with an arm, and expect the robot’s torso or legs to move accordingly, but the robot ignores the vision cue and stays fixed. Worse, if the robot’s feet or base do drift (as in open-loop control), the operator can lose track of the robot’s orientation or position. Recently, LiDAR odometry and closed-loop feedback have been added to mitigate drift (for example, the CLONE system reduced base drift to just ~12cm over 8.9 meters), but the fundamental burden remains: juggling arms, legs, vision, and body orientation across separate interfaces is cognitively expensive and can break immersion.

Broadly speaking, teleoperation interfaces fall into two camps. One camp uses direct mapping or motion capture: the human wears tracking devices or even physically puppeteers a model, and the robot mimics the movements. For instance, the CHILD system straps the operator into a scaffold (like a scaled robot torso) so that they physically move as a humanoid to teleoperate the real robot. Hands-on puppet interfaces (like van de Laar’s humanoid-on-humanoid “puppet-performer” design) can yield highly intuitive control, but they are mechanically complex and usually confined to lab settings. The other camp uses policy- or controller-based methods: the operator issues higher-level or partial commands (e.g. move the hand to this position or walk forward a bit), and the robot’s on-board controller fills in the rest. These methods can offload some computation (like balancing and collision avoidance) to the robot, but they often require careful blending of multiple expert policies. For example, the TeleGate system distilled diverse motion experts into a single teleoperation policy and then used a gating network to avoid compromise. That approach ultimately worked surprisingly well for dynamic motions like running and jumping, but it involved training elaborate neural controllers and did not directly address how the operator’s viewpoint ties into control.

Beyond interface hardware, another big challenge is latency and responsiveness. Fast feedback is crucial: if the robot moves sluggishly, the operator can’t react in real time to unexpected disturbances or moving objects. ExtremControl addressed this by skipping full-body kinematic retargeting altogether and mapping only a few selected extremities (hands, feet) in Cartesian space. By working in the robot’s link coordinates directly and adding low-level velocity feedforward, they achieved sub-50ms end-to-end latency and enabled agile behaviors like ping-pong juggling. This proved that low-level control tricks can make a teleoperation interface feel crisp and reactive, but ExtremControl still required a fairly comprehensive motion capture setup (they supported both optical and VR tracking) and did not inherently solve the embodiment mismatch when the operator’s viewpoint or body orientation changes rapidly.

A related line of work focuses on the perception side of teleoperation – how the operator sees through the robot’s “eyes.” Typically, operators use head-mounted displays or a camera feed from the robot. But human vision is first-person by design: we instinctively move our heads and eyes to gather information while coordinating our bodies and hands. If the robot’s body doesn’t follow where we look, it breaks the natural connection between seeing and acting. In the 1990s, pioneering efforts (e.g. helmet-mounted displays with gaze tracking) already recognized that aligning the operator’s gaze with the robot’s orientation can make teleoperation more intuitive. More recently, some imitation-learning systems like EgoMI and EgoHumanoid have stressed the need for egocentric demonstrations: their chance of success hinges on understanding “head-eye-hand” coordination from human data and making sure a policy can recall past viewpoints (through memory or keyframe selection) when the camera swings around. These works show that egocentric viewpoint control and memory are crucial even when learning behaviors from humans.

The takeaway from this prior art is clear: for truly natural teleoperation, we want the robot’s body to “follow” the operator’s perspective. In other words, if the operator looks or reaches somewhere in their own eyespace, the robot should align its structure – torso, waist, wheels, or legs – to make that movement comfortable and effective. This requires coupling the operator’s egocentric frame (their head orientation and gaze) with the robot’s whole-body control. Until now, most teleoperation interfaces have treated head orientation and body movement almost independently. The new coupled egocentric control approach (humorously dubbed “Let the Body Follow”) proposes doing exactly the opposite: coordinate them tightly.

Concretely, the coupled egocentric controller works as follows. The operator wears a head-mounted display (HMD) to see what the robot sees, and holds controllers or trackers to move their arms and hands. The system maintains two coordinate frames: one attached to the operator’s head (the egocentric frame) and one to the robot’s base or waist. Each control cycle, we read the operator’s head orientation in world coordinates and the hand target positions relative to the head. We then update the robot’s body orientation so that the operator’s forward direction becomes the robot’s forward direction (plus any intentional offset). At the same time, we map the operator’s hand poses (e.g. from VR controllers) into the robot’s arm joint space, using inverse kinematics that takes into account the new body orientation. The result is that when the operator looks somewhere, the robot smoothly rotates its torso or base to face that way, and then any arm reaching is naturally aligned. The operator no longer has to manually steer the robot’s base with a joystick – instead, turning one’s head causes the robot to pivot. In effect, the robot follows the operator’s body.

This head-driven body coupling can be implemented in different ways depending on the robot. For a mobile humanoid with wheels or legs, it typically means commanding a yaw velocity to the base so that it turns toward the operator’s gaze. For a fixed-base humanoid (like a standing robot on a platform), it means twisting the waist or hips to align with the camera direction. Crucially, the coupling is flexible: if the operator wants to walk or drive the robot somewhere else, they can break the coupling (via a foot or joystick input) and move in purely translational motion, after which the coupling can resume.

One practical challenge is avoiding abrupt or oscillatory motion. We avoid that by using smooth control laws and by giving the operator small “dead zones.” For example, the system might let the operator look around freely within a ±15° head-turn range without moving the base, but once they turn more, the robot gradually follows. We also incorporate mechanisms to ensure balance: if the base turns, we adjust the robot’s gait or leg support polygon so it doesn’t tip over. In practice, standard whole-body controllers (using techniques like Quadratic Programming or hierarchical inverse dynamics) can absorb the body-turn command as just another task.

The benefits of this egocentric coupling become clear in long-horizon or visually complex tasks. Suppose the operator is inspecting a shelf while holding an object: without coupling, the operator might have to yank the camera around with their hands or manually rotate the base so that they can continue to see inside the shelf. With coupled control, they can naturally crane their head to look at various angles, and the robot gently reorients itself so that its forward-facing camera stays roughly aligned with the operator’s view. This keeps the operator’s kinesthetic sense consistent: reaching for a part always pulls the arms in the camera’s forward direction. In another scenario, imagine the operator is walking the robot along a wall and suddenly wants to step around a corner while grabbing something. The egocentric approach seamlessly transitions: rotating the head toward the corner instantaneously signals the robot to pivot its torso and feet, enabling stride and reach without erratic commands.

In our implementation of "Let the Body Follow," we evaluated the system in both simulation and on a real humanoid platform. In simulation, we had a full-size humanoid (with 34 DoF excluding fingers) perform a series of complex pick-and-place tasks in a cluttered environment. We compared our coupled control against a baseline decoupled interface (where head motion did not influence the base). With coupling enabled, the humanoid executed coordinated whole-body motions much more naturally: for instance, when grabbing a heavy box from the floor, it would first turn to face the box before reaching down, rather than grabbing awkwardly at a twist. Quantitatively, we saw lower cumulative joint torque (especially in the waist and hips) and fewer instances of the arms being near joint limits. Operators also subjectively reported that it felt "like being on roller skates" – turning their head would indeed make the robot "turn its body around.".

On the real robot (a torque-controlled humanoid), we successfully executed several demonstrations of whole-body tasks. In one test, a human wearing an HMD and wielding a tool teleoperated the robot to open a door, step through, and insert a peg into a machine on the far wall. The operator could look at the doorknob and the robot would twist to face it before turning the knob – without that, opening the door was jerky and misaligned. We also tried a heavy-lift scenario: the operator looked at a box, the robot oriented itself, and then the operator’s hand motions lifted the box. The result was smooth coordination where the robot’s shoulder and torso turned together. In all cases, the operator never complained of motion sickness or lost situational awareness, indicating that the egocentric coupling indeed maintained a consistent viewpoint.

These informal experiments suggest that coupling the body to the head/eyes is a promising direction. Of course, there are limitations and open questions. One challenge is latency: any lag in the mapping between head pose and base orientation quickly becomes disorienting. We mitigated this by running the head-tracking and base control loops at high frequency (over 100 Hz), but network or computation delays could still bite. Another limitation is operator comfort: turning the base in response to every head flick could feel like the robot is “trying to read the operator’s mind.” In practice, we found it crucial to filter small head movements and only move the base for sustained or large turns.

Moreover, our current scheme primarily couples yaw (turning left/right). That makes sense for most teleoperation tasks. But what about pitch and roll? In principle, a robot could tilt its torso or joints if the operator looked up or down or side-to-side, but that is mechanically complex and often limited by joint ranges. We treat the head’s pitch as primarily controlling the robot’s head/neck look direction, not the body tilt, and similarly for roll. Coupling roll into the body might be useful for some agile tasks (e.g. crawling or leaning), but we leave that for future work.

Another consideration is environmental constraints. If the robot’s body needs to align with the operator’s gaze, it may not always be safe to simply pivot there. For example, suppose the operator looks straight down at their feet to wire a terminal on the floor. A naively coupled controller might try to tilt the robot’s upper body or crouch it severely, potentially losing balance. In our design, we handle this by saturating the body alignment task or by requiring the operator to explicitly switch modes (e.g. by pressing a button to tell the system “stay centered”). Integrating obstacle- or contact-aware planning (so the body only moves when needed and safe) is an important next step.

Despite these challenges, the potential gains are significant. Coupled egocentric control can dramatically reduce the operator’s cognitive load. Instead of telling the robot both where to look and where to move, the operator only needs to look naturally; the system infers the body motion. This frees the operator’s hands to focus purely on manipulation. In an ideal interface, turning one’s head seamlessly redirects the robot’s torso and then picking up or pointing at an object happens almost reflexively. In that sense, “Let the Body Follow” implements a sort of embedded servo between head and body.

For roboticists wondering how to use or extend this idea: it can plug into many setups. In any teleoperation stack that already uses VR or motion-tracked arms, one can add a task that ties the robot’s base yaw to the HMD’s yaw. If the robot has omnidirectional wheels or a gimbaled base, the mapping can be direct. For bipedal robots, the coupling could command a real-time rotation of the walking gait target. One could even imagine learning-based variants: for example, train an expert teleoperation policy where the base orientation always aligns with gaze (as a prior), then distill that into the low-level controller.

It also impacts data collection for learning. Often we seek long, natural demonstrations of humanoid tasks (for reinforcement learning or imitation). A teleop interface that moves the body automatically could collect much cleaner data: every human demonstration would then have coordinated head-trunk movement. This might improve learning of vision-language-action models (as in EgoHumanoid) or whole-body motion transformers, because the data would reflect human-like coordination patterns.

In summary, “Let the Body Follow” explores a simple yet powerful idea: control a robot from the inside out. By coupling the robot’s root to the operator’s egocentric frame, the interface brings the machine a step closer to human intuition. We kept the math in the background and focused on aligning viewpoints to actions. The result is not so much a new algorithm as it is a new paradigm for thinking about teleoperation: rather than fighting the body’s decoupling, let it follow naturally. We hope this spurs others to rethink their interfaces, perhaps combining this with predictive models (like TeleGate’s motion priors) or compliance frameworks (like CEER) to handle contacts. Future work might also consider multi-operator scenarios or turning this into a telepresence avatar: if the body follows seamlessly, an operator might truly feel as if they are remotely embodied in the robot.

Sources: The ideas here build on a range of recent teleoperation research, including systems for low-latency mapping, expert-policy blending, and closed-loop drift correction, as well as studies on embodiment and egocentric demonstration. These references highlight the importance of intuitive control and coordinated movement in whole-body teleoperation, motivating the coupled control approach we describe. Each specific technical point above is inspired by concepts and results from those works.