Skip to content

EMOS (The Embodied OS)

  • Software
  • Middleware
  • Framework

EMOS is an open-source runtime that turns quadrupeds, humanoids and mobile robots into Physical AI agents, driven by Python scripts called Recipes. It is built for ROS 2.

Made by automatika-robotics.

Source on GitHub: github.com/automatika-robotics/emos (opens in a new tab). Facts read at commit 93afccb (opens in a new tab).

Licenses

Code
MIT (opens in a new tab)

Read by Robotheca from LICENSE (opens in a new tab) (MIT) at commit 93afccb (opens in a new tab), on 22 Oct 2026.

Commercial use
Yes

What it does

  • Recipes are Python files that wire together perception, language-model, navigation and system components, and run on any supported robot without code changes.
  • Built from three layers: EmbodiedAgents for models and manipulation, Kompass for GPU-accelerated navigation, and Sugarcoat for lifecycle-managed ROS 2 components.
  • Runtime events can switch behaviour, for example falling back to a local model when a cloud API fails or running recovery when navigation gets stuck.
  • Cortex takes a task in plain language, builds a plan from the Recipe's capabilities, and replans when a step fails.
  • Auto-generates a web UI from a Recipe, with live telemetry, video and configuration, plus a JSON and WebSocket API, served over HTTPS.
  • Installed through a CLI in pixi, native or container modes; models can run locally or on servers such as Ollama, vLLM or LeRobot.

Written by Robotheca from the project's README (opens in a new tab) at commit 93afccb.

Getting started

Difficulty
Intermediate
Hardware it needs, as the project states it
Supports Linux with ROS 2 Humble, Jazzy or Kilted; pixi mode works on any Linux distribution and offers GPU builds where a CUDA toolkit is found. Requires Go 1.25+ only to build the CLI from source. Local models run on the robot itself; no further hardware is specified.

Maintenance

Status
Active: a commit in the last 90 days
Newest commit
22 Oct 2026 on main
Latest release
EMOS v0.8.0 (22 Oct 2026)

Checked on GitHub on 22 Oct 2026.

Robots that can run it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.