OhhO Docs

OhhO OS is layered so that one API works across every robot and either runtime.

OhhO OS is the ohho-os package on PyPI. The source is the public

OhhO OS ships a built-in, no-ROS navigation stack (ohho.nav) — the

The checked install is [Install](install.md). These are the same commands.

OhhO OS ships two runtimes behind one identical API. ROS-ness is a backend

Preview. Coming with ohho-os 1.2.0. Agent setup does not work end-to-end on the current release.

Install OhhO OS from PyPI and drive OmniBot in simulation. The source repository

Skills are reusable, named behaviors that run on any robot. They register with

OhhO OS gives every robot a persistent, queryable memory of what it has

OhhO OS is robot-agnostic by design. A capability model describes what a

OhhO OS does not stop at control. The same package collects demonstrations,

Prototype mission console.

From a box of parts to a robot that powers on.

Roadmap: protocol adapters beyond ROS 2.

Design any robot. For any industry.

Roadmap: maintenance workflow.

Roadmap checklist. Not a certification tool.

One link: OmniBot and the simulator, over ROSBridge or serial.

Collect. Label. Ship.

Roadmap: fleet operations.

Prototype workspace console.

Download a skill. Or sell one.

Give your robot a mind of its own.

Prototype cockpit.

Roadmap: scenario testing.

Prototype inference console.

Roadmap: robot security.

Turn demonstrations into policies.

Roadmap: a live twin.

Four cameras. One smart view.

This checklist verifies the honesty and accuracy of physical arm capabilities across the four target intelligence product pages: OhhO Train, OhhO Data, OhhO…