OpenMind builds open-source software that helps machines think, learn, and collaborate
gpt-4o
(or Gemini, Claude, or DeepSeek) 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.
Title | Description |
---|---|
Simple, modular architecture | Human-intelligible architecture with natural language data buses. |
All Python | 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 |
Includes a simple web-based debug display | Watch the system work (WebSim at http://localhost:8000). |
Preconfigured endpoints | Voice-to-Speech, OpenAI’s gpt-4o , DeepSeek, and multiple VLMs. |
src/run.py
which provides the following commands:
start
: Start an agent with a specified configconfig_name
: Name of the config file (without .json5
extension) in the /config
directory.--log-level
: Optional log level (default: INFO
). Use DEBUG
for detailed logs.--log-to-file
: Optional flag to log to logs/{config_name}.log
(default: False
).pre-commit install
. This ensures that pre-commit checks run before each commit. Additionally, you can manually trigger all checks by running pre-commit run --all-files
.
hints
and docstrings
for better code maintainability.