Shinro Studio
Shinro Studio is the IDE. Five modes, one tool. The unifying theme is ease of use: lowering the barrier to composition, scaffolding modules from vendor docs with an AI assistant, and updating deployed modules without halting the rest of the system.
The five modes
Blueprint
Visual hardware composition via the Blueprint Editor (React Flow). Drop a Jetson on the canvas, attach a LiDAR, wire a SLAM module into it. The shape of the robot becomes a graph you can rearrange.
Flow
Visual behavior composition. Patrol patterns, emergency stops, conditional actions. The behavior of the robot becomes the same kind of graph as its hardware — composable, inspectable, versionable.
Code
When visual composition stops being the right abstraction, the embedded Monaco IDE picks up the rest. Customize a module. Author one from scratch. Step through it with the integrated debugger, which is itself a debugger module — swap GDB, LLDB, or a vendor debugger in and out as the target requires.
Simulator
Today the Simulator is a frontend-light 3D viewer using Three.js + Rapier. This is a happy-path visual surface, not a production-grade physics simulation. MuJoCo, Gazebo, Isaac Sim, and others are planned as simulator modules managed by the Backend Kernel. Integration with formal-verification methods (Mununu and alternatives) and agentic-AI workflows (local models or MCP / API integration) is part of the same module-driven simulator roadmap.
Deployment Manager
Compile, validate, push to target hardware. Hot-swap of individual modules. Compile-on-target — no runtime imposed on the robot. The hardest component of the Studio, and currently partial.
Why this matters
The Blueprint Editor lowers the composition barrier. The AI assistant scaffolds modules from vendor docs. Hot-swap means a deployed module updates without halting the rest of the system. Together they compress the integration tax described in the Overview.
Deployment Manager — the standout
The Deployment Manager is the headline aspiration: fleet-wide updates, hands-off “the robot keeps working” experience, an operator surface that doesn’t require an on-site engineer for every change.
Be honest with the timeline. The mechanism — hot-swap on top of the Backend Kernel — is validated. The full operator UX is in active development. What you see today is the scaffolding; what’s coming is the experience.