The path depends on the hardware’s state: an already running stock OS, a brand-new SD card or a separate flight-controller flashing task. The target Flash Tool should assist with agent installation but does not replace the vendor imager or firmware-specific procedures.
The KairOS decision tree is fully described; its own installer and signed release channel have not yet been released.
KairOS repository ↗On this page +
Do not mix OS imaging and agent installation
Stock OS already booted
Use Mission Control Flash Tool: role + board → generated command → SSH installation.
Fresh SD card
First flash the vendor OS with the official imager, enable SSH, then return to the stock-OS flow.
FC firmware only
Use a separate Chromium WebUSB/WebSerial flow; a companion Agent is not required.
The complete Drone Agent or Ground Agent workflow
Boot vendor OS
Boot Raspberry Pi OS, Ubuntu, Armbian or a supported vendor Debian image.
Enable SSH
Create a user, configure networking and secure access; record the IP/hostname.
Open Flash Tool
Mission Control → Settings → Flash Tool.
Choose role
Air-side Drone Agent or ground-side Ground Agent.
Choose exact board
The target matrix includes Pi 4B, Pi Zero 2 W, Radxa CM3/CM4, Rock 5C Lite, Cubie A7Z and other profiles.
Run generated command
Copy the specific curl … | sudo bash command and run it over SSH.
Open local setup
Go to http://<board-ip>:8080 and complete onboarding/pairing.
Start with the official operating-system image
- Choose the official image for the exact board and architecture.
- Verify the checksum/signature if the vendor publishes them.
- Flash the card with the official imager and enable SSH through its settings or after first boot.
- Configure hostname, user and network without default credentials.
- After a successful boot, follow the stock-OS Agent flow instead of trying to flash the Agent as a full disk image when no such artifact exists.
FC flashing is a separate operation with its own risk
Mission Control can flash a supported FC through WebUSB/WebSerial in Chromium. This flow does not install Drone Agent on an SBC and must not run during flight or over an unstable remote link.
After installation, proceed by role rather than to a random page
Drone Agent setup
MAVLink, video, networking, local status and Mission Control handoff.
Ground Agent setup
WFB reception, AP, tethering, physical UI and client paths.
First Flight
Only after calibration, pre-flight checks, failsafe and bench validation.