I come from a regular swe background, but I've spent the last few months getting into robotics and trying to build a snow-clearing robot, so here's my noob notes:

First, very much expected. Both Google and Qwen have been building explicit spatial reasoning and spatial output capabilities in their models since last fall, gemini 3 was released with support for outputting trajectories for example. I only took a look at Robonav (more relevant for my needs) and its architecture and capabilities are inline with other similar models (eg nVidia's alpamayo).

Second, the overall architecture they describe mirrors what I've been working on: You have general purpose LLM that takes a look at the works and the task in front of it and reasons to break it down into subtasks and tool calls, and you can think of RoboNav and RoboManip as tool calls here. The harness keeps a memory and manages the context of the LLM and tools and keep looping until the objective is complete.

Consider the task of clearing snow off a driveway using this suite: An LLM (Qwen 3.7 plus) takes look at the driveway and decides which areas to clear. The harness then tells robotnav to go to an certain location, then robotnav takes over an runs in a loop until the robot is that that location. Then the harness tells robotmanip to use the plow to clear strip of snow. The harness will then call the planner LLM to plan an execute the next clearing and repeats until the driveway is clear.

So what' the issues? Well, they didn't release the weights, nor the training scripts so you can't actually use it. But also, it's all very research-y still, the models are "small" but still huge/expensive for current edge hardware. You'd still need lots of data collection, HITL, and fine-tuning and evals to make it work for your task. You'd also need a secondary safety system to make sure the models don't wreck something. But overall, I do expect robots to use an agent/model combo like this in prod in a few years.