> For the complete documentation index, see [llms.txt](https://docs.openmind.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openmind.com/developing/0_introduction.md).

# Introduction

![](/files/JYOEprytj2cDSUtPOjc8)

### What is OM1?

OM1 allows AI agents to be configured and deployed in both the digital and physical worlds. You can create *one* AI persona and run it in the cloud but also on physical robot hardware such as Quadrupeds, TurtleBot 4, and Humanoids.

With OM1, you can interact with OpenAI's `gpt-5.2` (or Gemini, Claude, DeepSeek, or Ollama for local inference) and shake hands with it, mediated by physical robot hardware controlled by one or more LLMs. Agents/robots built on OM1 can ingest data from multiple sources (the web, X/Twitter, cameras, and LIDAR) and can then tweet, explore your house, and help your kids with their math homework.

Since it's open source, *you* have control and can optimize the system for your home or workplace.

This guide offers an overview of the OM1 agent runtime system, helping developers understand its core components and workflows. Inside, you'll find explanations of OM1’s CLI commands, recommended project structure, step-by-step instructions for adding new inputs and actions, and guidance on configuring your agents and robots for different environments. Additionally, the guide includes practical development tips to streamline your workflow.

Whether you're just getting started with OM1 or looking to optimize an existing project, this guide will equip you with the tools and best practices to develop, deploy, and maintain high-performance agents and robots.

### OM1 Capabilities

| **Title**                    | **Description**                                                                                              |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Simple, modular architecture | Human-intelligible architecture with natural language data buses.                                            |
| All Go                       | Independent modules that are easy to maintain, debug, and extend.                                            |
| Easy to add new data inputs  | Seamlessly integrate new data without major changes to the existing architecture.                            |
| Easy to support new hardware | Via plugins for API endpoints and specific robot hardware.                                                   |
| Supports Standard Middleware | `ROS2`, `Zenoh`, and `CycloneDDS`                                                                            |
| Preconfigured endpoints      | Text-to-Speech, OpenAI's `gpt-4o`, DeepSeek, Gemini, Openrouter, Near AI, Ollama (local), and multiple VLMs. |
| Simulators                   | Gazebo, Isaac Sim (Coming Soon)                                                                              |

To get started with OM1, head over to [Installation Guide](/developing/1_get-started.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openmind.com/developing/0_introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.