Image credit: Lottie animation by Centre Robotics (LottieFiles Free, used with credit). · source
Here's something I've been thinking about a lot lately: we keep treating humanoid robots like they're just humans with metal parts. And honestly, I'm starting to think that's been a mistake.
This week, three separate research papers dropped that, on the surface, look like they're about completely different things. One's about dual-arm manipulation. Another's about teaching robots to move by watching videos. The third is about representing solution spaces for redundant systems. But when you read them together (and I did, with way too much coffee), they're all wrestling with the same fundamental tension: how do we let robots be robots while still doing human-like tasks?
The constraint problem nobody talks about enough. Let me start with the MC-MPPI paper from the RCI Lab, because it gets at something I initially thought was a solved problem. It's not.
Model Predictive Path Integral control (MPPI) is one of those techniques that sounds intimidating but is actually pretty elegant. You basically sample a bunch of possible futures, see which ones work out best, and steer toward those. The catch? Standard MPPI uses soft penalties for constraints. That means when you tell the robot "don't break the kinematic chain," it hears "try not to break the kinematic chain, but if you really want to..."
For a 14-degree-of-freedom dual-arm system where both arms are holding the same object, "try not to" isn't good enough. The researchers' solution is clever: they use a variational autoencoder to learn a compressed representation of the constraint manifold (basically, the space of all valid configurations), then do their planning in that latent space. The result runs at 100 Hz in real-time on actual hardware.
I should know the literature better here, but I think this is one of the first times someone's gotten hard constraint satisfaction working with sampling-based MPC at those speeds. The numbers they report for tracking accuracy are significantly better than baselines, though tbh the paper doesn't give exact percentage improvements in the abstract, so I'm working from their general claims.
Related coverage
More in Humanoids
A trio of arXiv papers this week suggests the field is converging on diffusion-based approaches trained on massive motion datasets, but the real bottleneck might not be algorithms.
James Chen · 12 mins ago · 5 min
Three new papers dropped this week that suggest we've been watching the wrong competition.
Sarah Williams · 13 mins ago · 4 min
A batch of new papers suggests we've been training robots the wrong way, and the fixes are surprisingly straightforward.
Sarah Williams · 2 hours ago · 6 min
Two new papers tackle robot safety with CBFs. The math is elegant. The gap between theory and messy reality is still enormous.
The geometric bias we've been ignoring. The Direct Dynamic Retargeting paper tackles a different problem, but it's philosophically related. When you want a humanoid to learn from watching human videos, you need to translate human motion into robot motion. The standard approach goes: video → human pose estimation → geometric retargeting to robot kinematics → then maybe some physics optimization.
The DDR researchers argue this pipeline has a fundamental flaw. By forcing the motion through a geometric retargeting step, you're constraining the robot to configurations that "look like" human poses. But the robot isn't human. It has different mass distributions, different joint limits, different actuator dynamics. What looks like a human walking motion might be dynamically terrible for a specific humanoid platform.
Their approach skips the geometric middle step entirely. They go straight from task-space objectives to physics-based trajectory optimization. The claim is that this "bypasses the geometric bias" and lets the robot find motions that achieve the same task outcome without being forced into human-shaped boxes.
I think this is a bigger deal than it might sound. We've built so much humanoid control infrastructure around the assumption that human motion is the target. But maybe the target should be human-like task completion, not human-like joint angles. These are different things, and we've been conflating them.
What does a solution space even look like? The third paper is more abstract, but it's the one that's been stuck in my head. It asks: for a redundant robot (one with more degrees of freedom than strictly necessary for a task), what's the shape of all possible solutions?
This matters because redundant robots don't have "a" solution to a task. They have infinite solutions that form continuous manifolds in configuration space. Current methods typically find individual solutions or trajectories using Jacobian-based techniques. That works fine for execution, but you lose information about the broader solution geometry.
The researchers propose learning an implicit representation of the entire solution manifold. Basically, a function that tells you how "close" any configuration is to being a valid solution. This gives you a distance field that encodes the structure of the solution space itself.
You might be wondering why this matters practically. Here's one reason: if you know the shape of your solution space, you can reason about which solutions are more robust (further from the boundary), which ones leave room for secondary objectives, and how solutions connect to each other. It's the difference between knowing one route through a city and having a map.
The thread connecting all three. Okay, so why am I lumping these together?
All three papers are, in different ways, pushing back against the idea that we should constrain robot behavior to match some predetermined geometric template. MC-MPPI does this by learning the shape of valid configurations rather than trying to penalty-function its way to feasibility. DDR does this by refusing to force robot motion through a human-shaped keyhole. The manifold paper does this by representing the full space of solutions rather than collapsing to individual trajectories.
There's a shift happening here, and I think it's significant. We're moving from "make the robot do this specific motion" toward "give the robot the tools to find motions that work for its body." That's a subtle but important distinction.
The practical implications are real. The MC-MPPI system runs on actual hardware doing actual manipulation tasks. The DDR approach shows measurably faster RL training convergence and better final performance on agile behaviors. These aren't just theoretical improvements.
What remains unclear. I want to be careful not to oversell this. A few things I'm uncertain about:
First, all three papers are tested on relatively controlled scenarios. The dual-arm system is doing manipulation in a structured environment. The DDR experiments focus on specific motion categories. We don't know yet how these approaches scale to messier real-world conditions.
Second, there's a compute and data question. Learning implicit manifold representations or VAE-based constraint encodings requires training data and computational resources that might not be available for every application. The papers don't fully address deployment constraints.
Third, and this is more philosophical, I'm not sure where the line is between "letting robots be robots" and "losing the benefits of human-like morphology." Humanoid robots are human-shaped for a reason. There's value in being able to operate in human environments with human tools. If we optimize too far away from human-like motion, do we lose something important?
Honestly, I don't have answers to these questions. But I think they're the right questions to be asking.
Where this is heading. If I had to guess (and this is speculation, not reporting), I'd say we're going to see more work that treats constraint satisfaction and solution space geometry as first-class concerns rather than afterthoughts. The VAE-based approach in MC-MPPI feels particularly promising because it's both principled and fast enough for real-time control.
The video imitation learning direction is interesting because it potentially unlocks huge amounts of training data. If you can learn from YouTube videos of humans doing tasks without being geometrically constrained to human poses, that's a much bigger data pool than robot-specific demonstrations.
And the implicit manifold representation stuff, while more academic right now, could eventually change how we think about motion planning entirely. Instead of planning trajectories, maybe we'll be navigating learned solution spaces.
I initially thought these were three unrelated papers that happened to land in the same week. After spending time with them, I think they're three views of the same emerging paradigm. We've been giving robots maps drawn for different bodies. It's time to let them make their own.