ADOSExtensions repository. Each released extension ships as a signed .adosplug archive on GitHub Releases and installs from a node’s Extensions page in Mission Control or with ados plugin install. Every extension is licensed GPL-3.0-or-later.
Each archive carries a SIGNATURE entry: the signer id and an Ed25519 signature over the archive’s canonical payload hash (every entry except SIGNATURE). The agent verifies it against /etc/ados/plugin-keys/<signer-id>.pem, refuses a signer, archive or release (<plugin_id>@<version>) listed in /etc/ados/plugin-revocations.json, and refuses the install when no enrolled key verifies it. See Signatures and trust.
The agent refuses an install on a board that is not in the extension’s board list (
* means any board).
MAVLink Gimbal v2
Drives a MAVLink gimbal-manager on component 154. Beyond manual pitch and yaw it runs a visual servo on the companion: click a detected subject in the cockpit and the gimbal keeps it centred. It stops commanding the moment the vision engine reports the subject uncertain or lost, and it never re-locks onto a different subject by itself. Cockpit Skills: Aim (
G), Recenter (Shift+C), Nadir (Shift+V) and Rate mode (Shift+G).
It speaks MAVLink Gimbal v2 only. A gimbal that does not present a gimbal-manager to the flight controller is not supported.
Permissions
command.sendevent.publishmavlink.component.gimbalmavlink.readmavlink.writemcp.exposetelemetry.extendtelemetry.subscribe.gimbalui.slot.flight-skillui.slot.node-detail-tabui.slot.settings-sectionvision.detection.subscribe
*
Navigation
Position hold when GPS is unreliable. A downward camera plus the flight controller’s gyro produce an optical-flow measurement about 30 times a second, sent as
OPTICAL_FLOW to ArduPilot and iNav and as OPTICAL_FLOW_RAD to PX4. With a LiDAR or a Visor’s stereo pair it runs a pose of its own (planar scan matching, 3D LiDAR odometry or stereo visual-inertial odometry), builds a live occupancy map and sweep cloud, and on ArduPilot sends the pose as ODOMETRY with automatic EKF source-set switching; a planar scan becomes OBSTACLE_DISTANCE for proximity avoidance. The pose, scan and map are shared topics the pilot, Capture and Mission Control’s Map tab read. The Engage Skill (Shift+N) turns it on and off.
Permissions
estimator.pose.injectevent.publishevent.subscribehardware.uartmavlink.component.viomavlink.readmavlink.writenetwork.listennetwork.outboundnode.info.readsensor.stream.readtelemetry.extendtelemetry.readtelemetry.subscribe.navigationui.slot.cockpit-panelui.slot.flight-skillui.slot.node-agent-pagevision.frame.read
*
See the Navigation guide.
Follow-Me
Click a subject in the live video and the drone follows it at a set distance and height above the ground. A detector on the companion produces detections, you designate one, and the companion locks that track, estimates the subject’s range from the feet ray, the box height and an optional planar LiDAR, tracks its velocity, and streams local-frame position, velocity feed-forward and yaw setpoints to the flight controller at 20 Hz. A downward rangefinder on the flight controller keeps the height above the terrain.
It stops commanding when the tracker reports the subject uncertain or lost. After a loss the operator-selectable re-acquire mode decides: Strict holds and waits for a new designation; Smart coasts on the prediction for a few seconds and re-designates a person who matches the subject’s appearance where the subject should be, announcing it. The tracker never re-locks silently. The Follow-Me Skill (
Shift+F) arms and disarms the behaviour and asks for confirmation first. An AI client gets two tools, follow_status and stop_follow, and no way to start a follow: a follow begins only when an operator designates a subject. See the Follow-Me guide.
Permissions
command.sendevent.publishevent.subscribeflight.motionmavlink.readmavlink.writemcp.exposetelemetry.readui.slot.flight-skillui.slot.node-detail-tabvision.detection.subscribevision.track.designate
cm4, cm5, rock-5c-lite, rk3588s2, rk3576, rpi5, cubie-a7s, cubie-a7z
SIYI optical pod
Speaks the SIYI Gimbal Camera External SDK over UDP, TCP or TTL serial, so the agent drives what a stock autopilot mount cannot: thermal palette and gain, the laser rangefinder and subject geolocation. On start it queries the firmware and hardware id, picks that model’s capability profile, and exposes only the controls the model supports.
Until the pod answers the identity query it is sent nothing. The query retries on a fixed interval with no attempt limit, so a pod powered on after boot comes online without a restart. Laser range plus gimbal angles plus the flight controller’s pose resolve a subject latitude and longitude, which the geolocate tool reports. Gimbal attitude and laser range are mirrored to the flight controller as standard MAVLink, so the built-in gimbal panel works too.
Permissions
command.sendevent.publishhardware.uartmavlink.component.cameramavlink.component.gimbalmavlink.readmavlink.writemcp.exposenetwork.outboundtelemetry.extendtelemetry.subscribe.siyiui.slot.cockpit-panelui.slot.flight-skillui.slot.node-detail-tabui.slot.settings-sectionui.slot.video-overlayvideo.source.set
cm4, cm5, rock-5c-lite, rk3588s2, rk3576, rpi5, generic-x86_64
Thermal camera
Development preview: no release archive is published, and capture needs a native UVC backend that the agent does not supply. With no backend, no device on the bus or a failed open, the extension publishes an explicit unavailable state with the reason and never reports a temperature.
The driver targets a FLIR Lepton 3.5 on a PureThermal 2 dongle. It locks the radiometric linear mode so raw counts convert to degrees Celsius, meters a centre spot plus the frame minimum and maximum, and colourizes the feed with palettes that match between the agent and the cockpit overlay. Cockpit Skills: Cycle palette (
Shift+O) and Flat field correction (Shift+I).
Permissions
event.publishhardware.usb.uvctelemetry.extendtelemetry.subscribe.camera.thermal.frametelemetry.subscribe.thermalui.slot.flight-skillui.slot.settings-sectionui.slot.video-overlayvideo.source.set
cm4, cm5, rock-5c-lite, rk3576, rk3566, generic-x86_64
Capture
Records 3D capture sessions on a drone or Visor: pose-tagged keyframes from every camera, plus the IMU, GNSS and Navigation’s LiDAR, posed by Navigation or the flight controller. Finished sessions upload to a reconstruction node, resumably and checksum-verified, and keyframes stream to it live while you fly. A ground station relays the radio lane onto its LAN.
Permissions
button.subscribecamera.control.writecapture.storage.writecloud.publishdisplay.oled.pageevent.publishevent.subscribemavlink.readmcp.exposenetwork.outboundnode.info.readplugin.http.com.altnautica.reconstructplugin.navigation.map.readradio.aux_streamsensor.stream.readsensors.rig.writetelemetry.extendtelemetry.readtelemetry.subscribe.statusui.slot.cockpit-panelui.slot.map-overlayui.slot.node-agent-pageui.slot.node-surfacevideo.whep.relayvision.frame.read
*
See Capture for setup, configuration and the API.
Reconstruct
Reconstructs captured sessions on a LAN compute node into a Gaussian splat, point cloud, mesh, occupancy and indoor products that Mission Control views, measures and exports. The same node runs perception offload for a drone with no on-board accelerator, returning detections to the drone’s own detection bus, and builds the full-resolution live map from a drone that streams its scans.
The installer turns it on by default for workstation and compute nodes. Its binaries download at install for the node’s own architecture, each checked against a SHA-256 pinned in the signed manifest.
Permissions
capture.storage.writecloud.recordsevent.subscribehardware.gpumcp.exposenetwork.listennetwork.outboundnode.info.readperception.readplugin.navigation.map.readtelemetry.extendtelemetry.readtelemetry.subscribe.statusui.slot.node-agent-pageui.slot.node-surfacevision.detection.publishvision.frame.readvision.offload.advertise
*
See Reconstruct for setup, configuration and the API.
Install one
From Mission Control:- Open the node, go to Agent, and under Software click Extensions.
- Pick the extension from the list of available extensions and click Install, or click Install from file and upload a downloaded
.adosplug. - Read the review page and click Install. The button names how many permissions the install grants.
ados plugin install takes a first-party catalog id, a release URL or a local archive:
Publish your own
Build an extension with the SDK, sign it with your own key, and install it from a local file or a URL; see Your first plugin and Distribution: local install. To list it in the registry, see Distribution: the registry.Next steps
Install from Mission Control
The per-node Extensions page and the install review.
Extensions on the agent
The CLI, signatures, permissions and isolation.