Become a
10x robotics engineer.
BRIO knows your TF trees, your hardware constraints, and your entire robotics workspace so you go from a broken launch file to a running node in minutes, not hours.
ROS2 · Custom stacks · Gazebo · Isaac Sim · VS Code
"I made BRIO because I spent countless hours debugging ROS2 workflows at previous startups and an aerospace R&D company. Now I have a founding robotics engineer always by my side."
An AI co-pilot that understands your robot.
BRIO is an AI development platform built for ROS 2 roboticists. A lightweight agent on your robot snapshots live state — TF tree, /diagnostics, node graph, topic activity — and ships it to a Claude-powered supervisor in the cloud.
The supervisor dispatches explorer and coder sub-agents that reason about the situation in the context of your code, then send tool calls back down to your machine — running bash, reading and writing files, editing launch configs, and patching nodes with you in the loop.
Ask "why is my costmap empty?" or "fix this TF chain" — BRIO inspects the actual running system, not just the source on disk.
A 3-zone TUI on your workstation. Streams agent output, services tool calls, and runs against your live robot.
$ curl -fsSL https://github.com/getbrio/brio-releases/releases/latest/download/install.sh | bash $ brio login $ brio
The same agent, in your editor. Inline diffs for node and launch-file edits, side-by-side with your terminal and ROS workspace.
Debugging async messages with AI is a nightmare
Current agents lack the context to trace root causes across nodes, or understand which custom message types are relevant.
Two nodes are publishing to /diagnostics. Which one is the culprit? The agent can't tell.
The Simulation Loop is Broken
Every change means Build → Launch → Observe. Crashes mean digging through stdout.
Gazebo loads. It's a syntax error.
Hardware is Unforgiving
Generic AI suggests solutions that run fine on your dev machine... and die on a Jetson.
It doesn't know your power budget, your latency envelope, or your sensor constraints. BRIO does.
Built for the
real stack.
Your robot.
In the field.
Stop debugging stack traces. BRIO handles your toolchain so you can focus on what the robot needs to do. Early access for teams shipping autonomous systems.
Ship your robots
faster and more safely than ever.
Join engineers building the next generation of autonomous systems. Early access is limited.