Skip to content
AI News HubLIVE
More
In-site rewrite1 min read

The Sequence AI of the Week #908: You Need to Learn About Gemini Robotics

Summary

Google put a walking humanoid inside a single policy, published the reasoning half as an API, and kept the motor half behind a partner gate. The numbers explain why.

SourceTheSequenceAuthor: Jesus Rodriguez
The Sequence AI of the Week #908: You Need to Learn About Gemini Robotics
Report an error

The correction channel is not available yet. You can copy the article reference below for later.

Correction instructions
Read article

The demo carrying this entire release is boring on purpose. You ask Apptronik’s Apollo 2 to put the watering can into the green bin on the bottom shelf. It walks to the table, picks up the can, takes a few steps to the shelves, and places it where you asked. Nothing in that sentence sounds hard until you remember what the previous Gemini Robotics models actually were. They were a torso bolted to a fixed base doing tabletop work. If there were legs, they belonged to somebody else’s controller. Walking is not the interesting part. Boston Dynamics solved walking years ago with hand-tuned controllers and a lot of hydraulics. The interesting part is that the walking and the grasping came out of the same policy, conditioned on the same language instruction. Locomotion stopped being a subsystem you call and became part of the action space you predict. That is the real news in Gemini Robotics 2, and it is a bigger deal than the b-roll makes it look. Three models, two access tiers Read more

Key points and analysis

Article intelligence

EngineersIntermediate

Key points

  • AI generation is temporarily unavailable; this entry was preserved with deterministic fallback metadata.
  • Google put a walking humanoid inside a single policy, published the reasoning half as an API, and kept the motor half behind a partner gate. The numbers explain why.

Highlights and analysis are generated automatically and may contain errors. Check the original source.