Skip to main content
Your code lives and runs on the robot. You edit it in place over SSH and it reloads on save, with nothing to build or sync.
No robot? The simulator runs the same workspace/, and everything below works the same way.

​
Open the robot in your editor

1

Check SSH works

Use the password that came with your robot. Your hostname is in the app under Configuration → WiFi. Other connection options: Connect via SSH.
2

Connect your editor

In Cursor, Windsurf, or VS Code with the Remote - SSH extension, run Remote-SSH: Connect to Host… from the command palette and enter jetson1@<hostname>.
3

Open the OS folder

Open /home/jetson1/innate-os/. The file tree, search, and terminal now all run on the robot.
Image to make: Editor connected to MARS. Screenshot of VS Code or Cursor connected over Remote SSH, with the innate-os folder open and workspace/custom_skills/ expanded in the file tree.

​
Where things live

Your two custom_* folders are gitignored, so updates never touch them.

​
Write your first skill

Follow Your first agent and skill. It takes five minutes and works the same on the robot as in the simulator.

​
When changes take effect

If a reload seems missed, innate service restart always works.
You don’t need a fork to build agents and skills. Fork innate-os when you want to version your work or change the OS itself. On the robot:
The robot’s startup service points at ~/innate-os/, so your clone launches on boot.