How to use embodiment starters

A starter kit is a project you clone and modify, not a library you install and use. It ships the project structure — build config, deps, wiring, entry script — for one specific use case. The developer clones it, fills in their specifics, runs it. They own the result; the starter has no ongoing version relationship to their project after clone.

If you're setting up hardware for the first time, start with Set up your embodiment — it walks the onboarding path fast. This page and the per-starter guides below are the deeper reference for what each kit contains.

Each starter targets the Linux workstation that drives the robot. macOS install paths are documented per-starter for developers scaffolding on a laptop before moving to the deploy machine.

Why starter kits

Some integrations need a project structure, not just a function call. Documenting "here's how to set up your project" in prose drifts and breaks. Shipping the same instructions as a working project — version-controlled, executable, copy-pasteable — is reliable.

Each starter encodes one opinionated path through the problem. It's not a framework with options; it's "here's how we'd do it." If you want a different shape later, throw the project away and start over from a different starter.

Available starter kits

Each row pairs a robot (the embodiment) with the model that drives it. A model name like MolmoAct-2 SO-101 identifies a specific checkpoint; the starter's docs explain what the model expects and produces.

More embodiments will land as we add them. The pattern is consistent: clone the repo, edit ~/.config/nt/nt.toml with your hardware specifics, run the entry script.