Gemini Robotics-ER 1.6 powers Boston Dynamics Spot

The headline figure in Gemini Robotics-ER 1.6 is the jump in instrument-reading accuracy from roughly 23% under ER 1.5 to 93% with agentic vision, a near-fourfold improvement on the single capability industrial customers care about most. Crucially, the base model without agentic vision scores 86%; the remaining seven points come from letting the model iteratively re-look at the gauge, zoom, crop and re-reason before committing to a reading. That inner loop is the real delta, and it was shaped, by DeepMind's own admission, through direct collaboration with Boston Dynamics on actual industrial faceplates rather than synthetic benchmarks.

The broader scorecard tells a consistent story about where the model is strong and where it is still thin. Pointing and counting land at 80% success, single-view success detection reaches 90%, multi-view success detection sits at 84%, and hazard identification edges out the general-purpose Gemini 3.0 Flash by six points on text and ten points on video. Those are the sub-skills a roving inspection robot needs stitched together: first point at the right valve, then count the right number of them, then read the gauge, then decide whether what it saw is a hazard. ER 1.6 is the first model in the family that hits acceptable numbers on every leg of that chain simultaneously, which is why the Spot integration arrived the same week the model did rather than months later.

Under the confident benchmark numbers sits a quiet admission from Carolina Parada that reframes the whole category: the internet simply does not contain enough tactile data to pretrain on. "There is lots of information on the web about how to pick up a pen," she told Spectrum, "but there is not a lot of data with touch sensing on the internet." Vision-language-action models are so strong today precisely because YouTube, image captions and instructional text give them a bottomless corpus about how the world looks. Nothing comparable exists for how the world feels, weighs, slips, or resists.

That matters for the Spot story because industrial inspection is the subset of robotics where vision-only reasoning is genuinely sufficient. Read a gauge, check a leak, count a drum: all of it lives in pixels. The Atlas humanoid roadmap announced at CES 2026 does not enjoy the same luxury. Loading laundry, opening a latched door or plugging in a cable are tactile-first tasks, and no amount of ER 1.6-style agentic re-looking will close that gap. DeepMind's decision to lead with Spot and inspection is therefore not just a product choice but a data-physics choice: they are shipping where the training distribution already supports high reliability, and staying quieter about the manipulation problems where it does not.

Perhaps the most interesting framing of this launch came not from DeepMind's blog but from robotics-focused Reddit threads, which quickly converged on a two-brain reading of the architecture. In their decomposition, ER 1.6 functions as the strategist, an embodied reasoner that plans, points, counts and decides what success looks like, while Gemini Robotics 1.5 VLA continues to serve as the motor-level executor that turns those plans into joint trajectories on the robot. Boston Dynamics' own engineering post reinforces this read by emphasizing that Gemini operates only through predefined Spot APIs and "can't invent new capabilities or control Spot beyond what is available." The planner is big and probabilistic; the action vocabulary underneath it is small and vetted.

That split is a significant departure from the monolithic end-to-end VLA dream that dominated robotics discourse a year ago. It suggests the commercially shippable path is not one giant model that maps pixels directly to motor torques, but a high-capability reasoner tethered to a narrow, well-characterized execution API. The upside is predictability, which is exactly what industrial buyers need before they let a robot near a live instrument panel. The downside, which some physical-AI commentators have flagged, is that each new capability still requires plumbing on the Boston Dynamics side; the strategist can only ask for moves the executor already knows how to perform.

On paper, a jump from 23% to 93% instrument-reading accuracy is the kind of step-change that justifies a product launch. In robotics-focused community threads it read differently. One frequently upvoted line, "93 percent is not going to cut it in industrial inspection," captured a practitioner instinct that seven percent residual error, applied across thousands of gauges per shift at a chemical or energy site, is not an engineering rounding error but an unacceptable operational liability. Darker jokes in the same threads imagined Gemini cheerfully confirming that a sulfuric acid pump was fine, minutes before it wasn't.

Marco da Silva's own framing, that Spot reaches acceptable field performance around 80% accuracy, sits uncomfortably next to that skepticism, because the number that matters in practice is not raw accuracy but the ratio of false positives to true catches. Crying wolf on an inspection route forces humans to re-check everything and erodes the autonomy gain the robot was sold on. A separate contrarian thread, led by a commenter asking simply "why not just use digital gauges," argues the whole category is a workaround for legacy PLC-and-analog infrastructure; rebuttals pointed out that retrofit costs, especially in government and heavy-industry settings, dwarf the cost of buying a Spot. The real read is that ER 1.6 has not ended the inspection-automation debate. It has moved it from "can a robot read a dial at all" to "at what false-alarm rate does a customer renew," which is a much more commercial, and much more interesting, argument.