Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.altnautica.com/llms.txt

Use this file to discover all available pages before exploring further.

​
CLI Reference

The public ados CLI is intentionally small. It helps you find the local setup webapp, check agent status, update the agent, and uninstall it. Configuration, pairing, MAVLink, video, ground-station setup, logs, and remote access are handled in the local setup webapp or ADOS Mission Control.

​
Commands

CommandUse it for
adosOpen the full-screen terminal status page when using a TTY. Prints plain status when run from a script or pipe.
ados statusPrint setup, MAVLink, video, network, remote access, and service status.
ados status --jsonPrint the full setup status payload for scripts and support tools.
ados updateCheck for and install an available agent update.
ados update --check-onlyCheck for updates without installing.
ados update --yesInstall without an interactive confirmation.
ados update --jsonPrint update check details as JSON.
ados uninstallRemove ADOS Drone Agent from the system.
ados uninstall --purgeRemove config in addition to package files and runtime data.
ados uninstall --yesSkip the uninstall confirmation prompt.

​
ados

Run ados after install or over SSH: 
ados
In an interactive terminal it opens a read-only status page with:
  • Setup URL.
  • Hotspot, LAN, USB tether, and mDNS URLs when available.
  • Mission Control and tunnel URLs when configured.
  • MAVLink and video state.
  • Network and remote access state.
  • Services and telemetry.
Press q or Ctrl-C to exit. If the command is not attached to a TTY, it prints the same summary as ados status.

​
ados status

Use ados status for a short support-friendly summary: 
ados status
Example output: 
ADOS Drone Agent 0.49.26
Device:  ADOS Agent (ados-1234)
Profile: drone
Setup:   67%

Open setup: http://ados.local:8080
MAVLink: False
Video:   running http://ados.local:8889/main/whep
Remote:  disabled

Next: Connect or configure the flight controller
For scripts: 
ados status --json
The JSON output is the same setup status used by the setup webapp and Mission Control.

​
ados update

Check and install updates: 
ados update
Check without installing: 
ados update --check-only
Run non-interactively: 
ados update --yes
Print machine-readable output: 
ados update --json

​
ados uninstall

Remove the installed agent: 
ados uninstall
Remove config as well: 
ados uninstall --purge
Run without prompts: 
ados uninstall --purge --yes

​
ados plugin

The ados plugin subgroup manages the agent plugin host: install, enable, disable, remove, inspect, and tail logs for installed plugins. Each plugin runs as a subprocess under the agent supervisor with its own cgroup limits and a capability-gated IPC channel.
CommandWhat it does
ados plugin listShow every installed plugin with state, version, and risk level.
ados plugin install <archive>Install a signed .adosplug archive from a local file or URL.
ados plugin enable <id>Start a previously installed plugin and add it to the supervisor’s restart set.
ados plugin disable <id>Stop the plugin and remove it from the restart set. The plugin stays installed.
ados plugin remove <id>Stop and uninstall the plugin. State on disk is purged.
ados plugin info <id>Print the manifest, declared permissions, signer, and last-known status.
ados plugin perms <id>Show permission grants. Add --revoke <perm> to drop one.
ados plugin logs <id>Tail the plugin’s structured logs.
ados plugin lint <archive>Static-analyze an archive: signature, manifest schema, banned imports, permission shape.
ados plugin test <plugin_dir>Run the plugin’s pytest suite against the test harness.
install, enable, disable, remove, and perms --revoke prompt for confirmation by default. Pass --yes to skip prompts in scripts. The full operator and OEM guide is at Plugins. Plugin authoring lives under the Developers tab.

​
Where the old commands went

The setup webapp is the operator UI for:
  • MAVLink setup.
  • Video setup.
  • Network and hotspot setup.
  • Cloudflare remote access.
  • Ground station pairing and role setup.
  • Logs and support status.
  • Advanced recovery.
Mission Control remains the main GCS for flight operations, hardware management, video, fleet state, and plugin workflows.