> 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/release-notes/major-updates/production_ready_release.md). # Production Ready Release ### Summary v1.0.0 marks the first production-ready release, delivering autonomous robotics capabilities. This release introduces full Gazebo simulation support, complete autonomy for Unitree G1 humanoid robots, over-the-air updates, and significant improvements to the developer experience through hot reload and configuration versioning. ### Core Services * OM1 * OM1-avatar * OM1-ros2-sdk * OM1-video-processor * OM1-OTA ### Key Highlights * Full Autonomy for Go2 and G1 * Local LLM integration * ML stack migration to NVIDIA Thor * Hot Reload * OTA updates * Gazebo integration for Go2 with OM1 * Pydantic-Based Configuration > **Note:** We're committed to continuous improvement and regular updates. Your feedback and contributions are invaluable in shaping the future of OM1. Join our community to stay updated on the latest developments! --- # 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/release-notes/major-updates/production_ready_release.md?ask=&goal= ``` `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.