Glossary
What Is RT-H?
Last reviewed: October 2026
Short answer
RT-H is a published robot policy (arXiv 2403.01823) that splits action prediction into two steps. It first predicts a fine-grained language motion such as “move arm forward” from the image and task, then predicts the action conditioned on that motion. People can correct it in language. It is third-party research, and Firsthand is not affiliated with its authors.
01
What is RT-H?
RT-H is introduced in RT-H: Action Hierarchies Using Language (arXiv 2403.01823) by Suneel Belkhale, Tianli Ding, Ted Xiao, Pierre Sermanet, Quan Vuong, Jonathan Tompson, Yevgen Chebotar, Debidatta Dwibedi and Dorsa Sadigh. The project page lists Google DeepMind Robotics and Stanford University as affiliations. The paper was submitted on 4 March 2024. RT-H builds an action hierarchy out of language: the policy goes from the high-level task to a language motion, and from the language motion to the action, using visual context at every stage.
02
Where does Firsthand fit next to RT-H?
RT-H is third-party research. Firsthand is not part of it or affiliated with its authors, and makes no claim that any model was trained on Firsthand data. What the site states is custom egocentric collection of real human demonstrations, fast and on demand, to a written spec: 3D hand pose at 21 joints per hand, calibrated stereo depth and 6-DoF IMUs at 200 Hz, delivered in RLDS, LeRobot format or WebDataset with a buyer-owned commercial license. The only language data the site states is one task instruction per episode. The site does not state language-motion labels, so this page makes no claim that Firsthand provides them.
03
What problem does RT-H address?
Per the abstract, language-conditioned policies share data between semantically similar tasks. As tasks become more semantically diverse, such as “pick coke can” and “pour cup”, sharing data gets harder, and mapping high-level tasks to actions needs much more demonstration data.
The authors’ insight is to teach the robot the language of actions, describing low-level motions with fine-grained phrases like “move arm forward” or “close gripper”. Predicting these language motions between task and action forces the policy to learn the low-level structure shared across disparate tasks.
04
How do action hierarchies using language work in RT-H?
The project page splits the policy into two queries. The language motion query predicts a fine-grained language motion from the image tokens and the task description tokens. The action query then decodes that language motion into actions, using the context of the task and the scene.
The page says RT-H uses a vision-language model co-trained on internet-scale data to predict both the language motion from the task and the action from the language motion. The same phrase, such as “move arm forward”, plays out differently depending on the task and scene.
05
How does correcting a robot in language work?
Because the action query is conditioned on a language motion, a person can step in with a different one, for example “move arm left” instead of “move arm forward”, and the policy follows it. To learn from corrections, only the language motion query is updated with the newly labelled corrections, and the updated model is deployed back into the hierarchy.
The authors report that policies trained this way can learn from such interventions and outperform methods that learn from teleoperated interventions.
06
What did the authors report?
On their Diverse+Kitchen multi-task dataset with eight evaluation tasks, the project page says RT-H outperforms RT-2 by 15% on average, and scores higher on six of the eight tasks. Replacing language with class labels drops performance significantly, and swapping the automated motion labelling for K-Means action clusters causes a minor drop.
For corrections, the page reports a rise from 40% to 63% with 30 intervention episodes per task. These are the authors’ claims on their own setups, and Firsthand does not reproduce them.
07
How is RT-H different from RT-1, RT-2 and Hi Robot?
The site’s RT-1 entry covers a Transformer that outputs an action from images and a task description, and its RT-2 entry covers a model that writes robot actions as text tokens. RT-H adds an intermediate language-motion step between task and action, and the authors compare it against RT-2 as their baseline. Whether the paper compares against RT-1 is Not stated in the text read.
The site’s Hi Robot entry covers a hierarchical system in which a high-level model outputs a simple language command for a low-level policy. The site’s VLA-OS entry lists RT-H and Hi Robot as examples of the Hierarchical-VLA category, which is VLA-OS’s grouping. How the RT-H authors relate their work to Hi Robot is Not stated in the sources read.
08
What data does RT-H use, and what language data does the site have?
The sources read describe multi-task robot datasets with an automated motion labelling procedure that produces the language motions. Dataset size, robot hardware and the number of demonstrations are Not stated in the sources read.
The sources read do not describe human egocentric video, stereo depth, hand pose or IMU data as part of RT-H’s training. On the site, the only language data is one task instruction per episode.
09
What is not stated, or still open, in the sources read?
The authors note that RT-H cannot zero-shot perform the novel tasks they tried, such as unstacking cups, and needs human intervention after the early phases; they present this as a sign of learning shared phases of tasks. Code, weights and licence are Not stated in the sources read.
10
When do you need custom egocentric data collection instead?
When a program needs real human egocentric demonstrations of tasks, environments or objects that public data does not cover, specified in writing. Firsthand does not build or train models.
Confirm the spec on a Spec Pilot, a small fast first batch. Where coverage is deep, the median from signed spec to first validated batch is 48 hours; where it is thin, three to four weeks. Billing is per validated hour.
11
RT-H at a glance, as stated in the official sources
| Item | What the sources state |
|---|---|
| Paper | RT-H: Action Hierarchies Using Language (arXiv 2403.01823) |
| Authors’ affiliations | Google DeepMind Robotics; Stanford University (project page) |
| Type | Language-conditioned robot policy with a language-motion action hierarchy |
| Stages | Task to language motion (language motion query), then language motion to action (action query) |
| Example language motions | “move arm forward”, “close gripper”, “move arm left” |
| Backbone | Vision-language model co-trained on internet-scale data (project page) |
| Code and licence | Not stated in the sources read |
| Firsthand relationship | None |
13
Results reported by the authors (project page; the authors’ own setups and baselines)
| Setting | What the authors report |
|---|---|
| RT-H against RT-2, Diverse+Kitchen, eight tasks | RT-H outperforms RT-2 by 15% on average; higher on 6 of 8 tasks |
| Language replaced by class labels (RT-H-OneHot) | Performance drops significantly |
| K-Means action clusters instead of motion labelling (RT-H-Cluster) | Minor drop |
| Learning from corrections (RT-H to RT-H-Intervene) | 40% to 63% with 30 intervention episodes per task; substantially outperforms RT-2-IWR |
| New scenes | RT-H and RT-H-Joint generalise 8–12% better on average than RT-2 |
| New objects | RT-H generalises 10% better on average than RT-2 |
| New tasks | Not zero-shot; shows promise with human intervention |
14
RT-H next to related terms on this site
| Term | Per the site | Relation to RT-H (per the sources read) |
|---|---|---|
| RT-1 | Transformer that outputs a robot action from images and a task description | Not stated in the text read |
| RT-2 | Vision-language-action model that writes robot actions as text tokens | The baseline RT-H is compared against |
| Hi Robot | Hierarchical system: a high-level model outputs a language command for a low-level policy | Not stated in the sources read; VLA-OS groups both as Hierarchical-VLA |
| Vision-language-action model | Maps a visual scene and a language instruction to an action | RT-H fits this definition; the sources read do not use the label |
15
RT-H versus custom egocentric capture
| Aspect | RT-H (per the sources read) | Custom egocentric capture (per the site) |
|---|---|---|
| What it is | A policy and its published results | A dataset delivered to a written spec |
| Goal | Share low-level structure across tasks and learn from language corrections | Real human demonstrations of the tasks a program specifies |
| Language data | Task descriptions plus language motions | One task instruction per episode |
| Source footage | Multi-task robot data | Real human egocentric capture |
| Hand data | Not stated in the sources read | 3D hand pose at 21 joints per hand |
| Depth and inertial | Not stated in the sources read | Calibrated stereo depth and 6-DoF IMUs at 200 Hz |
| Delivery | Code and licence not stated in the sources read | RLDS, LeRobot format or WebDataset, buyer-owned commercial license |
16
Frequently asked questions
- What is RT-H?
- A published robot policy (arXiv 2403.01823) that predicts a fine-grained language motion from the image and task, then predicts the action conditioned on it. It is third-party research.
- What are action hierarchies using language?
- Per the paper, a two-step policy: task to language motion, such as “move arm forward”, then language motion to action, with visual context at every stage.
- Is RT-H better than RT-2?
- The authors report RT-H outperforming RT-2 by 15% on average on their eight-task Diverse+Kitchen evaluation. These are the authors’ results on their own setups.
- Is RT-H a vision-language-action model?
- It maps a visual scene and a language instruction to an action, which fits the site’s definition. The sources read do not use the label themselves.
- Does Firsthand data train RT-H?
- No claim is made. Firsthand is not affiliated with its authors, and the site does not state that any model was trained on Firsthand data.
- Does Firsthand deliver language-motion labels?
- The only language data the site states is one task instruction per episode. Language-motion labels are not stated, and scope for any model is confirmed on a Spec Pilot.