# Adapting one robot policy across nine platforms

Octo is a generalist manipulation policy trained on the Open X-Embodiment dataset and evaluated as a reusable starting point for robots with different sensors, action spaces, and physical forms.

Canonical: https://brightaifuture.com/discoveries/octo-robot-policy-adaptation
Format: discovery
Source publication: 2024-05-20
Bright publication: 2026-09-19
Substantive update: None recorded
Evidence and review: Demonstrated; confidence: unassessed; source-checked; ai-assisted. AI-assisted comparison with the cited sources. Source-checked means the record was checked against those sources; it does not claim independent reproduction, expert review, or validation of the publisher’s results.

## The human problem

A new robot setup often needs a policy rebuilt from scarce demonstrations before it can attempt even familiar manipulation tasks.

## The prior constraint

Earlier generalist policies were often unavailable or locked to the observations and action spaces used during pretraining.

## AI’s actual role

A transformer-based diffusion policy converts language or goal-image instructions and robot observations into action sequences.

## The documented result

The Robotics: Science and Systems 2024 paper reports fine-tuning experiments across nine robot platforms, and the project publishes pretrained Octo 1.5 checkpoints plus training, fine-tuning, inference, and real-robot evaluation code.

## Why it may matter

Released code and weights give independent labs a common policy they can inspect and adapt, while physical safety and task reliability remain local responsibilities.

## Limitations

The experiments are research evaluations on specific tasks and hardware, not evidence of safe autonomous deployment. Repository code and the named Octo 1.5 checkpoint are MIT; the Open X-Embodiment source datasets still require their own provenance and terms review.

The reported cross-platform results come from the model authors and were published at RSS 2024. The project exposes MIT-licensed code and downloadable Octo 1.5 checkpoints; those artifacts do not establish unattended robot safety.

## Unresolved questions



## Provenance and history

{
  "dates": {
    "eventDate": null,
    "publicationDate": "2024-05-20",
    "captureDate": "2026-09-19",
    "lastReviewedDate": "2026-09-19"
  },
  "provenance": {
    "origin": "editorial",
    "externalId": "https://octo-models.github.io/paper.pdf"
  },
  "revisions": [
    {
      "id": "revision:open-models-added:octo-robot-policy-adaptation",
      "recordedAt": "2026-09-19",
      "summary": "Bright added this source-checked open-model application record. The cited source publication date is 2024-05-20; 2026-09-19 is when Bright added this record.",
      "sourceIds": [
        "octo-rss-2024-paper",
        "octo-model-repository",
        "octo-arxiv-paper"
      ]
    }
  ],
  "corrections": []
}

## Original sources

- [Octo: An Open-Source Generalist Robot Policy](https://octo-models.github.io/paper.pdf)
- [Octo generalist robot policy](https://github.com/octo-models/octo)
- [Octo: An Open-Source Generalist Robot Policy](https://arxiv.org/abs/2405.12213)

## Continue exploring

- [Open Models](https://brightaifuture.com/open-models)
- [Open intelligence](https://brightaifuture.com/worlds/open)
- [What changes when powerful models become open-weight?](https://brightaifuture.com/threads/open)
- [Someone builds on it](https://brightaifuture.com/open-intelligence)