Look fun to me, and you got me hook on the chess roasting robot. Wish I have spare USD2K for the robot hardware.

Just wondering what the main function of the open onboard agentic OS built on top of ROS2? Does it has a dedicated name or just plugin extension for ROS2.

The agentic OS allows to abstract away from ROS2 by creating the concept of "skills" that can be triggered by the agent; you don't really have to care anymore about defining nodes or racing conditions between them, our framework is a lottle simpler in that way. Triggering a skill is the equivalent (almost) to triggering an action in ROS2 btw.

But the interest of it is how it is packaged and that it can be triggered by this VLM-based agent called BASIC that we created.

This agent has a special kind of architecture which gives it spatial memory, capability to react in time, and ability to navigate. This means that skills can be triggered in the right place at the right time, like a true entity. BASIC can interrupt skills in execution depending on how you configure it. So that if it's chilling navigating around and it sees you, it would interrupt navigation and get to you, shake hands and ask if you need help instead of finishing the task without reacting.

Hope this helps!