Set up from any terminal, finish in the browser.


SETUP WEBAPP
One mobile-first flow.
The agent serves the webapp itself. It reads the same status object as the CLI, Mission Control, and the Android handoff, so every surface agrees.
Parameters without a laptop GCS
Read and write flight controller parameters from the agent's own page, on the hotspot or the LAN.


Every page, one checklist
Identify, MAVLink, video, network, remote access, Mission Control, finish. Required steps show as done or needing action.
- StatusProgress, access URLs, services
- MAVLinkFC link, baud, heartbeat, WebSocket URL
- VideoCamera, WHEP URL, recording, link stats
- NetworkHotspot, LAN, USB tether, mDNS, modem
- Remote accessOptional tunnel token and health
- System and logsServices, logs, version, support summary
- AdvancedFactory reset, config import and export
Flight controller at a glance
Autopilot, firmware, link state, and heartbeat, read from the same status object the CLI prints.


TERMINAL
The terminal console has its own page.
The ados command opens a tabbed operator console over SSH: vehicle, link, video, parameters, extensions, logs, system and settings.
▌ADOS my-drone DRONE ● FC ArduPilot DISARMED STABILIZE ⇄ local 12:00:00 1 Overview 2 Vehicle 3 Link 4 Video 5 Params 6 Extensions 7 Logs 8 System 9 Settings ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │● HEALTHY │ │paired · cloud relay │ │╭ ▌ Links ──────────────────────────────────────────╮╭ ▌ Autopilot ──────────────────────────────────────────────────╮│ ││Console ││● ArduPilot connected STABILIZE DISARMED ││ ││Setup & dashboard in a browser, on this LAN. ││/dev/ttyACM0 · 115200 ││ ││➜ http://my-drone.local:8080/setup ● ││██████████████████████████battery 92% ████████████████████ ││ ││➜ http://192.168.1.50:8080/setup ││▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ ││ ││ ││GPS 3D sats 14 alt 0.3 m ││ ││Connect to GCS ││ ││ ││Add this drone to Mission Control - paste one of ││ ││ ││these into the Add-a-Node card (LAN pairing). │╰───────────────────────────────────────────────────────────────╯│ ││➜ http://my-drone.local:8080 ● │╭ ▌ Video ──────────────────────────────────────────────────────╮│ ││➜ http://192.168.1.50:8080 ││● running ││ ││ │╰───────────────────────────────────────────────────────────────╯│ ││Ground control │╭ ▌ Link ───────────────────────────────────────────────────────╮│ ││Conventional MAVLink over TCP / WebSocket for a ││cloud paired (https://command.altnautica.com) ││ ││third-party GCS: tcp://…:5760 for a desktop ground ││remote disabled ││ ││station, ws://…:8765/ for a browser GCS. ││hotspot off ││ ││➜ tcp://my-drone.local:5760 ● │╰───────────────────────────────────────────────────────────────╯│ ││➜ ws://my-drone.local:8765/ │╭ ▌ Services ───────────────────────────────────────────────────╮│ ││➜ tcp://192.168.1.50:5760 ││● 11 running ○ 0 stopped ││ ││➜ ws://192.168.1.50:8765/ ││hardware 4 ok ││ ││ ││ ││ ││Video ││ ││ ││Live camera in a browser (WHEP viewer). ││ ││ ││➜ http://my-drone.local:8889/main/ ● ││ ││ ││➜ http://192.168.1.50:8889/main/ ││ ││ ││ ││ ││ ││Mission Control ││ ││ ││Open Mission Control to fly this drone. Hosted at ││ ││ ││command.altnautica.com; a local or self-hosted │╰───────────────────────────────────────────────────────────────╯│ ││build runs wherever you serve it (e.g. │╭ ▌ Sensors ────────────────────────────────────────────────────╮│ ││http://localhost:4000). ││sensors imu 400/400 Hz · gnss 10/10 Hz · camera 30/30 Hz ││ │╰───────────────────────────────────────────────────╯╰───────────────────────────────────────────────────────────────╯│ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ paired · cloud relay ^K palette · a actions · ? help · q quit v0.106.3
- ados
- Open the terminal console
- ados status
- Print setup, MAVLink, video, network, remote access, and service state
- ados status --json
- Return the status payload for scripts
- ados pair
- Show this node's pairing information for Mission Control
- ados update
- Re-run the installer in upgrade mode to the latest version
- ados uninstall
- Remove the agent from the system
ACCESS
Local paths first, tunnel second.
MAVLink and video work over the LAN, a USB tether, or the agent hotspot before any cloud link. Lead with the board IP; the mDNS name resolves on the same network.
http://<board-ip>:8080Setup webapp and status over the LANhttp://<hostname>.local:8080mDNS on the same networkhttp://192.168.4.1:8080The agent hotspot, before any networkhttp://192.168.7.1:8080USB tether from a laptop or phonews://<board-ip>:8765Raw MAVLink WebSocket relayhttp://<board-ip>:8080/whepWebRTC video (WHEP)GO DEEPER
Explore the agent.
Install, SSH in, run ados.
The terminal prints the local setup URL. Open it and finish from any device.
Read the docs