Fundamentals

Gemini Robotics 2: What Evolved from the 1.x Line

Google DeepMind released Gemini Robotics 2 on 30 July 2026: three models that ship as a set and divide the job of running a robot between them. One reasons about the scene and plans, one turns those plans into motion, and a third runs on the robot's own hardware. The change that matters most is that a single model now drives a humanoid's whole body, walking and crouching and balancing included, rather than only its arms.
Published2026-08-0313 min read

01The three models

The three are not variants of one another. They occupy different layers of the same stack — deciding, moving, and running on the robot itself — and a working system uses more than one of them at a time.

PLANS

Gemini Robotics ER 2

The vision-language model that acts as the agent: it reasons about the physical scene, talks to people, calls digital tools, and breaks a mission into steps for the action model. Built on Gemini 3.5 Flash.

  • Tracks progress from continuous video
  • Coordinates several robots at once
  • Publicly available via the Gemini API
MOVES

Gemini Robotics 2

The vision-language-action model that turns vision and language into motor control. This is the one that gained whole-body control and multi-finger dexterity in this release.

  • Drives a humanoid from feet to fingertips
  • Also drives bi-arm rigs and simple grippers
  • Early-access partners only
RUNS LOCALLY

Gemini Robotics On-Device 2

A smaller VLA built to run on the robot's own hardware with no internet connection, and to be retargeted to an unfamiliar robot body quickly.

  • Adapts to a new body in a few hours
  • Typically fewer than 200 examples
  • Trusted-tester access only

Splitting the work this way is what DeepMind's own safety report calls a "system 2 / system 1" architecture: a deliberate planner on top, a fast reflexive controller underneath. It also explains why only one of the three is openly available to developers, which the access section below returns to.

Google DeepMind's own overview of the release, covering all three models in one reel.

02What changed since 1.x

Version 2 is the fifth release in a line that opened in March 2025, and the three lines have advanced on separate clocks ever since. Laid side by side, the jump from 1.x looks different in each of them.

VLA

1.5 to 2

  • Arms only to feet-to-fingertips
  • Grippers to 22-DOF five-finger hands
  • Tabletop reach to walking, crouching, balancing

Gemini Robotics 1.5 already ran on ALOHA 2, Apollo and bi-arm Franka rigs, but everything it did was arm work: grasping, sorting, placing. Version 2 takes over the legs and torso as well, so reaching a low shelf or the floor is part of the same policy instead of something a separate controller has to arrange.

ER

1.5 and 1.6 to 2

  • Still images to continuous video
  • One robot to orchestrating several
  • Gauge reading added in 1.6, still evaluated in 2

Gemini Robotics-ER 1.5 led 15 academic embodied-reasoning benchmarks on aggregate; 1.6 sharpened pointing, counting and multi-view understanding, and added gauge reading with Boston Dynamics. ER 2's change is about time rather than accuracy: working from continuous video instead of stills is what lets it say when a step finished, not only what is in frame.

ON-DEVICE

Gemini Robotics On-Device to 2

  • 2025: a new task from 50-100 demonstrations
  • 2026: a new robot body in a few hours, under 200 examples
  • Tested on ALOHA, Franka FR3 and Apollo since 2025

This is the only one of the three with nothing in between: Gemini Robotics On-Device landed in June 2025, and the next thing DeepMind announced for the line was version 2, roughly 13 months later. The 2025 model adapted to a new task from 50 to 100 demonstrations; the 2026 model is quoted on a different axis, adapting to an entirely new robot body in a few hours from fewer than 200 examples. The two are not a like-for-like improvement, because one counts new tasks and the other new hardware.

Not everything was replaced. The two mechanisms 1.5 introduced are the ones version 2 pushes further: Motion Transfer, which carries a skill demonstrated on one robot body over to a different one, and an internal reasoning step in natural language before acting. Read that way, whole-body control and minutes-long planning are less new departures than those two ideas taken further.

Versions so far

The reasoning model has shipped three times without a matching action-model release, because it is the half developers can reach through an ordinary API. The name shifted with this release too: it was written Gemini Robotics-ER through 1.6, and Gemini Robotics ER 2 without the hyphen from version 2 onward.

DateEvent
2025-03Gemini Robotics and Gemini Robotics-ER launch together, built on Gemini 2.0, restricted to trusted testers including Agile Robots, Agility Robotics, Boston Dynamics and Enchanted Tools.
2025-06Gemini Robotics On-Device: the first version built to run locally on a robot rather than in a data centre.
2025-09Gemini Robotics 1.5 and Gemini Robotics-ER 1.5 add Motion Transfer, which carries skills learned on one robot body over to a different one, and a step where the model reasons in natural language before acting.
2026-04Gemini Robotics-ER 1.6 improves pointing, counting and multi-view understanding, and adds gauge reading, developed with Boston Dynamics.
2026-07Gemini Robotics 2, Gemini Robotics ER 2 and Gemini Robotics On-Device 2 arrive together, and the hyphen in the ER name is dropped: whole-body control, multi-finger dexterity, multi-robot collaboration, and the ASIMOV-Agentic safety benchmark.

03Whole-body control

Earlier Gemini Robotics models were, in practice, upper-body models. They moved arms and hands across a table, and anything outside that reach was somebody else's problem. Gemini Robotics 2 adds the legs and torso, and with them the robot's centre of gravity, so it can step, squat and bend toward a target instead of being limited to what already sits in front of it.

DeepMind's worked example is the instruction "put the watering can into the green bin in the bottom shelf." Apptronik's Apollo 2 humanoid walks to the table, picks the can up, walks to the shelves and places it, with the model handling both the navigation and the balance that reaching a bottom shelf requires.

Official Google DeepMind footage of intelligent whole-body control: Apollo 2 walking, crouching and stabilising itself while manipulating objects, which is the specific behaviour that separates Gemini Robotics 2 from the arms-only generation before it.

Success rates

76.3%
Pick up from a shelf
68.4%
Pick up from a table
45.7%
Pick up from the floor

Reported success rates for general whole-body manipulation on Apollo 2 fitted with Inspire hands.

The floor figure is the one worth sitting with. Reaching down for an object on the ground is the case that most needs whole-body control, and it is also where the published number is lowest, which is a fair summary of how new this capability is.

04Dexterity

The second addition is control of hands complex enough to be hard to program by hand. Gemini Robotics 2 drives Apollo 2 fitted with five-fingered SharpaWave hands carrying 22 degrees of freedom, and also drives ordinary two-fingered parallel grippers, such as a Robotiq gripper on a Franka Duo. That range matters commercially: most robots already deployed in industry have a simple gripper, not an anthropomorphic hand.

The task list DeepMind published is deliberately fiddly. Tying a knot in a bin bag, sealing a ziplock, sweeping into a dustpan and screwing a light bulb into a socket all need continuous force adjustment against an object that moves as you work on it.

Official Google DeepMind footage of the dexterity work, showing the five-fingered hand tasks the published success rates above were measured on.

Five-finger hands

Reported task success rates, Apollo 2 with SharpaWave hands

Unscrew a light bulb
92%
Tie a bin bag
44%
Seal a ziplock bag
40%
Screw in a light bulb
36%
Sweep into a dustpan
32%

Unscrewing a bulb and screwing one back in are nearly the same motion in reverse, and the gap between the two published rates is the widest in the set. Removal tolerates approximation, because the thread guides itself once it catches. Insertion does not: the bulb has to be aligned before any force is useful.

Two-finger grippers

Two-fingered grippers score higher across the board on the tasks DeepMind reported for them, precise insertion included. A more capable hand, in other words, is not automatically a more reliable one.

05Multi-robot collaboration

The third addition belongs to ER 2 rather than to the action model. One reasoning model can now hold a plan across several robots at once, hand each of them the part of the job its body suits, and keep track of who has finished what. DeepMind's demonstration pairs an Apollo 2 humanoid with a Franka F3 Duo bi-arm manipulator; a separate build uses ER 2 to orchestrate Boston Dynamics' Spot through its navigation and manipulator APIs.

What makes this practical is a change in what ER 2 watches. It reads a continuous video feed rather than still frames, so it can judge when a step is actually finished, notice when one has failed, and re-plan mid-task. DeepMind describes tasks that run for several minutes across hundreds of decisions, a horizon that a model working from single snapshots cannot supervise.

Official Google DeepMind footage of multi-robot collaboration, with a humanoid and a bi-arm manipulator working the same task under one reasoning model.

Benchmarks

Reported accuracy (%), ER 2 vs. the strongest model each benchmark was compared against
Gemini Robotics ER 2Strongest model compared against

Real-robot control (vs. Gemini Robotics-ER 1.6)

60.0
48.6

Stopping when a human comes within 1 m (vs. GPT 5.6 Sol)

93.0
83.4

Success detection from an image (vs. Claude Opus 5)

87.7
83.6

Embodied question answering, ERQA (vs. Gemini 3.6 Flash)

78.5
73.0

Progress classification (vs. GPT 5.6 Sol)

57.4
46.2

Progress classification is the weakest of these in absolute terms, and it is also the one the multi-robot case depends on most: a coordinator that cannot reliably tell how far along a task is will hand out the next instruction at the wrong moment.

06Safety evaluation

Alongside the models, DeepMind published a safety report and released its benchmark, ASIMOV-Agentic, as a public dataset. The argument it makes is that physical safeguards such as emergency stops and speed limits remain necessary but are no longer sufficient, because a model that plans its own sub-tasks can walk into a hazard before any of those safeguards has anything to react to.

ASIMOV-Agentic

What ASIMOV-Agentic scores

  • Refusing a task that breaks a stated operating constraint, such as a payload limit or a rule against touching unsealed food containers, and saying why.
  • Triggering a protective stop mid-task when a safety monitor reports a hardware fault, a loss of stability, or a human coming too close.
  • Declining to hand the action model a task it has no training for, rather than letting it improvise a trajectory it cannot be trusted on.
  • Asking the operator to clarify an ambiguous instruction — "put the belt in the green tray" with two different belts on the table — instead of guessing.

The results are uneven in an instructive way. Every frontier model tested, ER 2 included, scored 100% on reacting to structured safety messages, which is the part closest to conventional software. Judging whether a task is feasible in the first place depended heavily on how much the model had been told about the action model's training: accuracy ran from 62.0% with no such briefing to 95.8% with the most detailed one.

What the report leaves out

The report is also explicit about its own scope, and that matters more than any single figure in it. It evaluates high-level semantic reasoning only, and names three things a compliant physical deployment needs that it does not assess:

Outside the safety report's scope

  • Certified hardware: components qualified against a functional-safety standard, rather than assessed only by how the model behaves.
  • Redundancy mechanisms: the arrangements that keep a machine failing safely when one part of it stops working.
  • Real-time guarantees: a bounded, provable time from detecting a hazard to actually stopping, not just a correct decision to stop.

Scoring well here is not the same as being cleared to work next to people. That layer is separate engineering work, governed by standards such as ISO/TS 15066.

07Access

Only the reasoning model is generally available. The two action models remain behind an early-access programme, which is the same posture DeepMind took with every previous Gemini Robotics VLA.

Availability

Who can use which model

  • Gemini Robotics ER 2 — public preview through the Gemini API and Google AI Studio, with a private preview on the Gemini Enterprise Agent Platform.
  • The previous-generation ER 1.6 preview is deprecated, with a shutdown date of 31 August 2026 and ER 2 named as its replacement.
  • Gemini Robotics 2 (the VLA) — early-access partners only, via a sign-up form. No public API.
  • Gemini Robotics On-Device 2 — trusted testers only, with a waitlist for early access.

Supported hardware

The hardware side is broader than the headline humanoid. DeepMind names Apptronik, Boston Dynamics and Agile Robots as partners, and its reported evaluations span Apollo 2, the Franka Duo, and, for the on-device model, Dexmate, Trossen and SO-101 platforms, the last of which is a low-cost open-source arm.

Related reading

Robot Foundation Models: Market Size, Players, and the Funding Boom

Who else is building robot foundation models, how the money has moved, and how large the market actually is.

Read more

08FAQ

Can I use Gemini Robotics 2 on my own robot today?

Only the reasoning half. Gemini Robotics ER 2 is in public preview through the Gemini API and Google AI Studio, so you can have it look at a scene and produce a plan. The two models that actually generate motion — the VLA and the on-device VLA — are limited to early-access partners and trusted testers, so a full stack still needs an arrangement with DeepMind.

What is the difference between this and NVIDIA's Isaac GR00T?

They sit at the same layer of the stack — a foundation model that outputs robot actions — but they are sold differently. NVIDIA publishes GR00T's model weights for developers to download and fine-tune, and pairs it with simulation tools and its own compute hardware. DeepMind keeps the Gemini Robotics action models behind an access programme and offers only the reasoning model as an API.

Why are some of the published success rates so low?

Because they are generalist figures, not figures for a task the model was purpose-built for. A conventional industrial robot screwing in the same bulb, in a fixed jig, at a fixed position, would be far more reliable and would fail completely if the bulb moved two centimetres. The Gemini Robotics numbers describe a model attempting tasks it was not individually programmed for, which is a different claim and a much harder one.

Does the safety report mean these robots are certified to work near people?

No, and the report says so directly. It evaluates whether the model makes sound high-level decisions — refusing unsafe instructions, calling a stop, asking for clarification — and states that it does not assess the certified hardware, redundancy mechanisms or real-time guarantees required for a compliant physical deployment. That layer is separate work, governed by standards such as ISO/TS 15066.

09Sources

Related articles

Share this articlePost on X
03

Robot Foundation Models

  • ›Gemini Robotics 2(this article)
04

Hardware Fundamentals

05

Movement & Perception Fundamentals