Skip to content

0.62.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 02:34
· 188 commits to main since this release

Altnautica Command v0.62.0

This release covers everything since 0.61.0: sixty-eight commits between
2026-10-22 and 2026-11-10. Three threads run through it.

The first is the cockpit, rebuilt as one full-viewport flight screen. A top
bar carries the flight-state chip, the status pill and STOP; flight actions
sit in a left column, the camera controls in a right column, the telemetry in
a bottom row, and the centre keeps the picture with an Instruments level for
the attitude instruments. Data layers (AR route, obstacles, depth, surfaces
and targets) draw in one canvas over the video, dim and hide when their data
goes stale, and ask the drone only for what is on screen through view leases.
A Fly button opens the flight screen from the fleet rows and the drone page.

The second is the drone's ADOS Pilot. The cockpit streams sticks and actions
to the pilot, shows who flies the drone in the flight-state chip, and offers
the Mode sheet, a skill picker, a Launch sheet and Fly here through the pilot.
Built-in actions fall back to the flight controller when the pilot stalls. A
DualShock 4 follows a shared binding table with gimbal rate on L2/R2 and a
designate reticle on the touchpad, and Settings › Aircraft setup runs the
agent's ground and air setup wizards.

The third is the ground underneath: maps show when the plan on the drone
differs from this device's plan, ground-station pairing sends the fleet key
the agent expects, and a round of refactors splits the largest client,
protocol, Convex and panel modules and generates the agent's API types.

Added

  • Flight screen. The cockpit is one full-viewport grid: a top bar
    (flight-state chip, status pill, battery with time to reserve, link,
    navigation source, controller, layer level, Menu, STOP), a left column of
    flight actions, a right column with the shutter, photo/video, zoom and
    camera settings, a centre for the picture and the layers, a bottom-left card
    that switches between map, attitude and obstacles by swipe or dots, the
    D/H/H.S/V.S/AGL bottom row, and a follow dock above it while following.
    Portrait stacks the picture, the actions, the readouts and the map. Items
    that do not fit the top bar move into the Menu. The flight instruments draw
    only at the Instruments level and shrink to fit a short centre.

  • Fly button. The fleet rows and the drone page open the flight screen.

  • Fly here through the pilot. Under ADOS control, when the drone's pilot
    takes a go-to, Fly here sends the map point to the pilot whatever runs now
    (a mission, a skill, a flight mode), and the hold dialog says it takes over.
    In FC manual or ELRS control it repositions the flight controller. A refusal
    (for example while launching, or while the flight controller flies a
    failsafe return or landing) is shown with its reason.

  • Mission ETA. The active mission chip shows the next waypoint's ETA from
    the drone's AR frame.

  • ELRS control mode. The Mode sheet offers the ELRS control mode when the
    drone is reached through a ground station.

  • Status pill FC warnings. The status pill lists the flight controller
    warnings the pilot reports, and the bottom row's AGL reads the pilot's
    height above ground; when the pilot's reading goes stale the cell shows no
    data instead of falling back to another source.

  • Layer unavailable chips below the top bar. A layer's "unavailable" chip
    stacks centred a fifth down the picture, as on the agent cockpit, so the top
    bar no longer covers it.

  • Designate reticle and gimbal rate on the controller. L2 and R2 drive the
    gimbal pitch rate through the agent, and the touchpad opens a designate
    reticle. The cockpit asks for a button press before a pad reports, shows the
    pad's product name and the first-connect tour, and reads "not supported" for
    a pad without the standard layout.

  • Plan banner on every map. Every full map view carries the plan banner,
    and when the plan on the drone differs the route drawn is the agent's copy
    of the drone's mission.

  • Aircraft setup (Settings › Aircraft setup). The selected drone's agent
    runs the ground and air setup wizards (detection, frame, accelerometer,
    level, compass, airspeed, radio, the ADOS switch position, motor and control
    surface checks, battery, initial tune, notch, the FC parameter profile, Meet
    ADOS Pilot; first hover or flight, trims, airspeed and TECS, autotune,
    verify). Each step is drawn from the agent's step schema with the cockpit
    spec's text and pictures: live values, progress, the motor question, inputs,
    blockers, results, and tap, hold or props-off hold confirms. Any finished
    step can be run again on its own, parameter snapshots can be restored, and
    the setup report lists each step's numbers. Demo mode plays a quad through
    the ground wizard.

  • Aircraft setup entry points. The flight-state chip's NOT READY state
    shows "Set up aircraft" when the drone reports aircraft setup is needed, and
    the first time Mission Control sees a flight controller without a completed
    ground setup a banner offers the wizard (once per aircraft).

  • Cockpit views. V (or Triangle on a controller) cycles Pilot, Map
    (the map main with the video as a picture-in-picture, which draws no data
    layers), Split (video beside the map) and Vision (the video with the
    detection list, model picker, depth options and engine summary at the
    side). O cycles the data-layer level; the layer button and the view button
    sit next to the flight-state chip, with the controller status.

  • Reduced update rate over a radio link. When the drone's live nav stream
    cannot open but its HTTP API answers, the cockpit polls
    GET /api/v1/nav/status at 2 Hz with its view lease and shows "Reduced
    update rate (radio)". Each value keeps its age on the drone.

  • Launch sheet. With the drone's pilot reachable, Take off opens Launch:
    take-off altitude, the after-take-off action (hold, a behaviour skill, start
    the loaded mission, or go to a point) and an optional when-done action. One
    1.5 s hold sends the sequence; the pilot's progress shows as a step strip,
    and Pause aborts it.

  • Flight-flow chrome. The handover banner, the "Centre sticks to take
    control" ring, "Sticks are with " with a Take over hold, the
    low-battery return-home countdown with Cancel, the link-loss countdown,
    voice prompts (handovers, return home, low battery, mission started, paused
    and complete; on by default) and optional on-screen sticks, all in the
    shared cockpit words.

  • Controller bindings from the shared table. PS pauses and held 2 s
    returns home (PS again cancels), L1 + R1 held 2 s with the left stick
    centred arms, L2 + R2 + Circle held 3 s is the emergency stop, the D-pad
    moves through the skill picker and steps the focused parameter (the layer
    level with the picker closed), Cross starts a skill and Circle stops it,
    Triangle cycles the view and held takes off or lands, Options opens quick
    settings, Options + D-pad changes the profile, Share records and Square
    takes a photo. Each action rumbles; on a secure origin a granted DualShock 4
    lightbar follows the flight state. A controller hold confirms a hold-tier
    action by itself (an incomplete checklist still opens the sheet).

  • Settings › Controls. The controller drawing with every control's
    action, live input, per-gesture editing, locked safety bindings that can
    only be moved, conflict highlighting that blocks Save, Mode 1 / Mode 2,
    stick calibration with the deadzone, rumble and lightbar tests, reset,
    export and import of the shared controls file, the first-connect tour,
    on-screen sticks and voice prompts.

  • Pre-flight checklist items for the ADOS Pilot's readiness, a live link,
    a connected controller when the pilot flies the sticks, and drone storage.

  • Plan on drone. Mission uploads record the MISSION_ACK plan identity;
    the cockpit's map views say "Plan on drone differs from this device's
    plan" when the drone holds another plan, with Load from drone.

  • Pilot stream. With an agent-connected drone, the cockpit opens
    WS /api/v1/pilot/stream (ticket scope pilot.control). In ados control
    mode the gamepad's sticks go to the drone's pilot as pilot.v1 input frames
    at 50 Hz, with a radial deadzone of 0.08 by default (the pilot applies the
    expo); the stream sends release when the pad disconnects, the tab is
    hidden or the pad stops reporting for 150 ms. fc_manual and direct-serial
    links keep the RC override. A pad must report the standard layout or carry
    a calibration from the calibration wizard before it streams.

  • Flight-state chip and Mode sheet. A chip at the top left shows who flies
    the drone (READY, PILOT · NORMAL, the skill, MISSION · WP n/N, RTH, FC ·
    mode with Take control, LINK when the pilot state is stale) with the
    secondary line for hold reason, avoidance and control mode, in the cockpit
    spec's words and colours. Tapping it opens the Mode sheet: profile, control
    mode (hold to confirm), avoidance (hold to turn off), hand to FC, VTOL
    transition and the FC modes.

  • Skill picker. The visible skill bar is replaced by a picker at the
    bottom right: tabs Behaviors / Camera / Navigation / Utility, each plugin's
    skills grouped under it, a Tweak panel for the skill's parameters, GO and
    Stop. One motion skill runs at a time; a skill that does not echo its state
    within 3 s reverts with a toast. Skills that exclude the drone's vehicle
    class are hidden. The loadout still holds keyboard bindings.

  • Left column. Take off / Land, Return home and Pause sit at the left,
    vertically centred.

  • Mission state. Mission overlays, the pause/resume binding and the
    upload guard read one mission state (none, loaded, active, paused,
    complete, returning): the drone's own when its agent publishes one,
    otherwise computed from the link's HEARTBEAT custom mode, MISSION_CURRENT
    (with its total, mission_state and mission_id fields, now decoded) and
    MISSION_ITEM_REACHED. Flight-mode names no longer decide it.

  • Demo pilot. Demo mode answers the pilot stream: sticks take the demo
    drone to PILOT, and Mode sheet actions change its state.

  • Cockpit data layers in one canvas. A layer stack over the main video
    draws every data layer in the cockpit spec's z-order: depth, surfaces,
    obstacles, targets (detection glyphs, cockpit marks, lead reticle), AR route
    and AR motion. Overlay frames from the agent's nav stream (ar,
    obstacles, depth, surfaces) live in a mutable store outside React; a
    change-driven draw loop interpolates keyed AR items between frames, fades
    items in and out over 120 ms, dims a layer after 500 ms and hides it after
    2 s with an "unavailable" chip, stops while the tab is hidden and caps at
    30 fps on a TV/kiosk. The level (Full / Route / Off) and per-layer switches
    persist per vehicle. The PiP draws no layers.

  • View and vision leases. The layer stack names the camera and layers it
    shows on the nav stream ({"type":"view"}, renewed every 2 s, released when
    hidden), so the agent computes overlays only for what is watched; the depth
    and surfaces layers hold a vision-demand lease of their own kind.

  • Vision view. The detection preview moved from the Perception tab into
    the cockpit: a side panel with the live detection list, the model picker,
    depth style and range, and the engine summary.

  • ADOS Pilot state on the nav stream. The pilot kind is parsed into the
    nav-stream store for the flight-state chip. Demo mode streams ar,
    obstacles, depth and surfaces frames built from the agent's golden
    wire fixtures.

  • Link key on the ground station's Video Link panel. A "Link key" row
    shows the ground station's control-plane key state from /api/video/config
    (hopping.key_status): bound (neutral), waiting for key (cold start) or key
    unavailable (both warnings). It is hidden when the agent does not report it.
    Demo mode serves a bound ground station.

  • HUD v2 target symbology. One resolver (lib/vision/target-state.ts)
    decides every target state on every video surface: candidate hairline,
    tracked brackets, locked, acquiring, following (filled TRACK tag, range and
    ±2σ tags, centre reticle, feet tick), holding, coasting (dashed brackets at the
    prediction, ghost path), searching (ring sweep, or an edge arrow with the
    bearing when the prediction is off-frame), re-acquired (snap plus toast) and
    lost (900 ms fade). States carry a word, not only a colour. The PiP and every
    other video preview draw their own camera's targets; reduced motion and the
    minimal layer drop animation and blur.

  • Following chrome. A range panel (range, ±2σ interval, AGL with its
    source, depression, bearing, target speed, range cues, pipeline latency), a
    right rail (follow / stop, STRICT | SMART re-acquire toggle written to the
    follow-me config, front ⇄ belly swap and record), and the re-acquire toggle
    on the follow skill.

  • Nav-source chip. Shows in the top bar what the EKF navigates
    on (DR, EXT NAV, GPS 3D·14, FLOW) and a quality word, from
    EKF_STATUS_REPORT, the GPS fix, the EK3 source-set parameters and the
    vision-nav state. Its popover decodes source sets 1-3 and switches the active
    set with hold-to-confirm.

  • Navigation feed. lib/agent/nav-stream.ts opens the agent's
    /api/v1/nav/stream (ticketed like the detection stream) and polls
    /api/v1/map/live for changed occupancy tiles; the follow, nav, pose, scan
    and map-status frames land in nav-stream-store.

  • Local-frame minimap and lidar radar. Without a GNSS position (or when the
    active source is external nav) the minimap switches to a north/east metre
    frame with live occupancy tiles, the SLAM trail, scan returns, the follow
    target and the drone; an AUTO | LOCAL | MAP toggle pins it. The proximity
    radar adds scan dots, 3/6/12 m scales with auto-select, and a LIDAR rate
    header.

  • Node Map tab. Mapping status (session, points, area, pose health, compute
    placement, memory against budget, voxel size, keyframes dropped, upload or
    stream progress), the live local map and a launcher for the mapping
    extension's 3D viewer.

  • Demo mode cycles every target state with matching follow, nav, pose, scan,
    occupancy and map-status data, gives the PiP camera its own boxes, and opens
    a labelled demo viewer (occupancy and a synthetic point cloud) from the Map
    tab's "Open 3D viewer".

  • GPS_GLOBAL_ORIGIN (49) is decoded and requested on connect, so the
    minimap's map mode places the follow target from its local position.

  • The Perception hub says when the detector backend is unavailable or a test
    stand-in instead of showing it as a working detector.

Changed

  • Calibration and autotune through the drone's agent. On a drone whose
    agent runs the setup engine, the accelerometer, gyro, compass, level,
    airspeed and radio calibration panels and the autotune sections (ArduPilot
    PID tuning, PX4 autotune) run that one setup step on the agent and show it
    live, instead of sending MAVLink. A flight controller on a direct serial
    link keeps the MAVLink panels; Betaflight and iNav panels are unchanged.

  • Setup wizard text. A step body variant the spec lacks falls back to the
    step's body, and an enum choice is labelled from the spec (for example
    "LiPo") rather than its raw value.

  • Cockpit width classes follow the shared spec: medium is 600–839 px and
    expanded starts at 840 px (was 1024).

  • The gamepad radial and the old cockpit gamepad shortcuts are removed
    (L1 + R1 quick settings, D-pad stream cycling, Start to leave immersive,
    Share to open the radial): the controller binding table owns every button.
    o and v are reserved for the layer level and the view cycle.

  • Built-in flight actions follow the shared cockpit table. Labels, arm
    gates, confirm tiers (Arm and Disarm hold 800 ms, Take off, Land and Return
    home hold 1.5 s, Emergency stop hold 3 s then confirm) and keyboard chords
    (shift+a, shift+t, shift+l, shift+r, space Pause, shift+p
    Resume, shift+c Take control, shift+x Emergency stop) come from the
    cockpit spec. While the pilot has the drone, each built-in is sent as a pilot
    action. Return home and Land are disabled on a stale link; Pause and
    Emergency stop are still sent blind. A new Take control action hands the
    drone back to the pilot. FC mode presets moved out of the default loadout
    to the Mode sheet.

  • Detection runs on demand. A view that draws detection overlays for a
    drone camera (the cockpit target layer, the picture-in-picture inset, the
    Perception preview and other video previews) asks the drone to detect on the
    camera it shows: it holds a lease through POST /api/vision/demand
    (owner: "mission-control:<id>", a random id per window so one window's
    release never cancels another's lease, 6 s, renewed every 2 s) over the
    direct LAN link while it is open and the page is visible, and releases it
    (hold_s: 0) when it closes, switches camera or the page hides. Views on
    the same camera in one window share one lease. The always-on detection
    listener holds none. With no boxes arriving, the overlay says why: detector
    idle, no detector on this camera (the agent refused the camera), drone
    refused the pairing key (401/403), detection needs a direct link, or
    detector unreachable.

  • A designated or followed target is drawn in the tracking colour instead of
    the green lock colour, and the lock brackets no longer pulse; the what's-locked
    chip reports the follow phase (following, coasting, searching, holding, lost,
    re-acquired).

  • [ and ] cycle a focus ring over drawn targets and preempt a skill
    binding on the same key while targets are drawn; Enter opens the target
    menu. A drag on empty video designates a box.

  • The follow skill shows the follow phase as a badge (acquiring, coasting,
    searching, holding with its reason, lost).

  • Built-ins fall back to the flight controller when the pilot stops
    answering, so Pause, Return home and Land still reach the drone.

  • Vision model picker. Only a detection model can be made the engine
    detector, and the cockpit picker lists detection models only. The armed
    lock reads the picker's own drone.

  • Extension skills. A stopped extension is named with its reason, a skill
    excluded for the vehicle class is refused on keys and the controller too,
    and default keys left unbound by a clash are listed in Settings › Controls.

  • Agent-run ground calibrations hold while the drone is armed.

  • The pilot stream's frames are checked key for key against the agent's
    shared request fixtures.

  • Large modules are split into directories (agent client, protocol adapter,
    Convex pairing, plugins, flight logs, telemetry recorder, video player,
    large panels) with public function paths unchanged.

  • The demo flight controller reports an external-nav source set with optical
    flow and GPS fallback sets, and its EKF flags follow the commanded set.

  • The error page, LED panel, 3D motor view, mission route, overview map and
    theme swatches read design tokens instead of literal colours.

  • The default picture-in-picture corner is bottom-left, clear of the radar and
    the follow rail; the stream tabs and the top-left widget column sit beside
    and below the larger minimap.

  • Writes of mavlink.source, serial_port, baud_rate, system_id and
    component_id that the agent refuses while armed ask the operator and, on
    confirm, resend with the force override; the FC-source port and baud are
    resent with the source as one change.

  • The what's-locked chip words are translated.

  • The stack deployer (tools/deploy, 0.1.1) now builds on the shared
    ados-term crate for its theme, terminal backend, progress renderers,
    widgets and command runner instead of carrying its own copy.

  • The agent's status, setup-status and heartbeat types are generated from the
    agent's JSON Schemas (src/lib/agent/agent-api.generated.ts,
    convex/lib/agentHeartbeat.generated.ts); a test checks every heartbeat key
    has a Convex validator.

  • The telemetry deck raises severity alerts for every metric, not only the
    ones on the visible page.

  • Fewer re-renders during flight: freshness hooks subscribe to their own
    channel, the map memoizes its markers and lines, and the deck reads one
    metric table.

Fixed

  • Flight screen. The centre marks and flight instruments sit on the
    video's centre (the video pane's in Split view), where the boxes and route
    are drawn. The bottom row keeps the latched home position for D, and AGL
    never shows height above home: only a rangefinder or the terrain report.
    The status pill ages out stale pilot readiness and FC text, warns when the
    pilot stops answering instead of reading "All systems OK", and lists a
    "PreArm:" line once, as a pre-arm warning, on the ground only. Plan
    identity counts the ArduPilot home slot, claims no difference without a
    reported total, and "Load from drone" no longer leaves "Plan on drone
    differs" on ArduPilot. The follow
    dock clears the Vision side panel; the touchpad reticle opens only where a
    target layer can draw it; cockpit marks draw without a detector and
    "Targets unavailable" shows only for a running detector; the page under
    the flight screen is inert; Take off / Land, RTH and Pause stay on screen
    with the skill layer off; the attitude radar dims an unknown heading; a
    layer switch no longer saves the class default level for the vehicle. The
    bottom-left card's map fills the card again: it had collapsed to nothing,
    leaving an empty panel with no tiles, drone or route.

  • Gimbal rate. The right column gains a press-and-hold gimbal pad, shown
    only when the drone reports it takes gimbal rates. Rates are quantised, sent
    one at a time at about 10 Hz with the zero never overtaken, and back off on
    a rate limit. Space stays Pause while the pad is held.

  • Detection boxes go stale visibly. Boxes dim at 500 ms and hide at 2 s
    with a "Targets unavailable" chip.

  • The cockpit map no longer sits under the flight-state chip. The minimap
    is the bottom-left card at the spec's size for each width class, so the top
    left holds only the chip row; the stream tabs and top-left widgets moved
    below it, and the camera roster and picture-in-picture moved above the map.

  • Pilot actions report refusals. Built-ins flown through the drone's
    pilot, the Mode sheet, the Launch sheet and F1/F2/F3 now carry an action id
    and wait up to 3 s for the pilot's answer; a refusal, a closed stream or no
    answer shows as a failure with the pilot's reason instead of reading as
    sent.

  • Overlay keep-alives no longer restart interpolation. A repeated frame
    refreshes only the layer's freshness clock; items interpolate over the time
    between distinct frames, bounded to 16–250 ms.

  • Mode-sheet changes stop motion skills. A control-mode change, a hand-over
    to the flight controller, and pause, land, return home, kill or an FC mode
    change end any active motion skill; navigation and camera skills keep
    running.

  • Skill picker freshness. A plugin state older than 3 s dims its entry with
    "last seen N s"; on a lost link an active skill reads "Active (stale)" and its
    Stop is queued until the link returns.

  • Flight-state chip distances. GOTO distance is the vehicle against the
    goal (it read 0 m on every clear path) and RTH distance is the vehicle
    against the flight controller's home.

  • F1/F2/F3 pick the Cine/Normal/Sport flight profile and are reserved from
    skill bindings.

  • Target boxes ease inside the layer canvas. Tracked boxes ease toward each
    new detection in the canvas draw loop; the per-frame React smoothing loop is
    removed. Tag fonts are cached, and the focus ring allocates nothing per frame.

  • Layer chips use the spec's unavailable-chip colour and are localised.

  • The layer stack no longer re-renders while frames stream. The cockpit's
    layout context value is stable between renders and the layer stack is
    memoised, so telemetry-rate cockpit renders stop reaching it (163 commits in
    10 s before, 0 after).

  • Settings › Controls shows the saved bindings after a reload. The draft
    followed the default table when the store hydrated after the first render;
    it now follows the saved table until the first edit.

  • Plugin skill state reports refresh the skill picker at once. A report
    from a plugin (active, idle, disabled) now recomputes the picker and bar;
    before, it waited for an unrelated vehicle-state change.

  • Demo mode lists the SIYI pod's eight camera skills and Follow-Me's tweak
    parameters in the skill picker.

  • Pairing a ground station with a drone failed every time. The Pair modal
    sent the retired typed pair_key, which the agent refuses. It now sends the
    fleet radio key as base64 (blob_b64), the drone's device ID, and optionally
    the drone's half of the key (shared_key_b64) so the station can verify
    presence beacons. It shows the reply's paired device ID, fleet slot, key
    fingerprint and beacon-key outcome, explains each agent error code in plain
    words, and offers unpair-and-retry only when the station holds a different
    fleet key. Demo mode pairs against an in-memory ground station.

  • The perception chip carried a leftover inline offset that pushed it onto the
    speed tape; it now stacks in its zone.

  • Setting the operating region could leave a half-written posture. The
    region panel now sends one setup apply (regulatory: {mode, region}), so the
    agent writes both fields together and records the operator acknowledgement.

  • The live video player no longer appends a newer segment ahead of a queued
    one; a dropped segment now jumps to the live edge, and a failed append is
    retried after trimming instead of being lost.

  • Calibration timers in demo mode stop on disconnect.

  • Electron's socket bridge ignores malformed send/close arguments, and the
    updater accepts commands only from the main window.

Security

  • tools/deploy/deploy.sh runs only a release binary that passes the minisign
    signature on SHA256SUMS and its checksum line, cached per version under
    ${XDG_CACHE_HOME:-$HOME/.cache}/ados-deploy/<version>. Without minisign, or
    on any verification failure, it builds from source. It no longer runs an
    unversioned ./ados-deploy from the checkout, and Windows shells (Git Bash,
    MSYS, Cygwin) now get the Windows release asset.
  • Next.js 16.4.5, DOMPurify 3.4.17, zod 4.6.7, fast-uri 3.1.9 and ip-address
    10.7.6 for published security advisories (within the declared version
    ranges).

Removed

  • Abort. The Abort action is gone; Pause covers it.
  • Old cockpit chrome. The status band, the telemetry strip, the top-right
    actions, the skill bar controls, the HUD readouts, the follow rail's hold,
    return and land mirrors, and the layout editor's chrome toggles with their
    saved flags are replaced by the flight screen.
All 74 commits since v0.61.0
  • Desktop Release: one draft release before the parallel builds; refuse to publish a release missing an installer (fc8961b)
  • Fix MSE append ordering, apply regional posture in one setup call, guard Electron IPC args (bb1ae7e)
  • Cut telemetry re-renders: per-channel fresh hook, shared metric table, memoized map layers (4395362)
  • Type protocol diagnostics hooks, track every mock calibration timer, share FC section card and domain types (a3bd038)
  • Split Convex pairing, plugin, flight-log and status modules; public function paths unchanged (64d3b7a)
  • Split agent client logging, system, vision, plugin and type modules into directories (64a044c)
  • Split telemetry recorder, MSE player, dataflash converter, client manager and large panels (dacbddb)
  • Split protocol adapter, callback and command modules; remove re-export shims (f6bad74)
  • Use generated agent status, setup and heartbeat types; add heartbeat key parity test (7c2be03)
  • Deployer runs on ados-term; deploy.sh runs only a signature- and checksum-verified release binary (a37cdcb)
  • Changelog: generated agent types, region apply, video append order, deployer (d110d0d)
  • HUD target, lead, coast and ground-truth tokens; HUD roles locked above theme blocks; detection boxes only from the active stream's camera (991c5d1)
  • HUD v2 cockpit: target states on every video surface, follow range panel and rail, nav-source chip with source-set switch, local-frame minimap with occupancy and scan, radar scan dots, node Map tab, agent nav stream; demo autonomy cycle; armed-override on link tuning and MAVLink config; GPS global origin; benchmark-only model badge (2b80cb9)
  • Map products in a north-aligned map_ned frame (FC heading latched at the map origin), so the SLAM map overlays LOCAL_POSITION_NED (49e2187)
  • agent client: remove the unused profile-choice call (4efcfbb)
  • radio panel: show the ground station's link key state (364d31d)
  • ground station: pair with the fleet key blob and read the agent's pair reply (863fefe)
  • video link panel: neutral bound key, changelog, render test (9fdcb3c)
  • ground station pair: stop on a failed unpair, label the key halves, keep the fleet roster in demo (8c5561a)
  • ground station pair: unpair drops the fleet roster and beacon key (36f7904)
  • Vision overlays hold an on-demand detection lease on the camera they show (d94f9bf)
  • Detection lease: per-window owner, refused pairing key shown apart from a refused camera (52ba2e2)
  • Cockpit spec: byte copy of the shared cockpit tables (built-ins, controller map, layout, layers, views, flight-state chip, colours) (3fc51cf)
  • Cockpit spec: controller drawings, setup strings and illustrations (byte copy) (249757c)
  • Design tokens: cockpit overlay and flight-state colours (AR, data layers, flight state) (9e58975)
  • Cockpit spec: setup strings for the flight-controller steps' inputs, blockers, live values and PX4 accelerometer text (byte copy) (53f424b)
  • plugins: regenerate the agent contract registry (pilot.v1) (f41b6fd)
  • Cockpit spec: setup strings for skipped steps (byte copy) (917b4fc)
  • cockpit: data layers in one canvas with view and vision leases (68694e7)
  • cockpit: pilot stream, flight-state chip, Mode sheet, skill picker, spec built-ins, one mission state (94b2f70)
  • cockpit layers: allocation-free steady draw, golden obstacles and pilot fixtures (9c65b42)
  • cockpit layers: browser test seam for layer switches (231dcd9)
  • pilot stream: session id is a non-zero u32, as pilot.v1 decodes it (651047d)
  • cockpit: views, controller bindings with rumble and lightbar, Settings > Controls, Launch sheet, flight-flow banners and voice, on-screen sticks, pre-flight pilot items, plan identity, radio poll fallback; stick routing and liveness fixes (2b88145)
  • models: MiDaS v2.1 small depth model in the registry (ONNX, CPU runtime) for the depth and landing-zone layers (eac5e71)
  • controller bindings: a press gesture fires on button-down while a hold on the same control keeps timing (baf74d5)
  • cockpit spec: press gesture for the PS brake and the Options+Circle fallback (with its RTH hold), hold label, plain description (a9e9aa0)
  • cockpit: pilot actions await their result and show refusals; keep-alive frames keep interpolation; motion skills stop on mode changes; F1-F3 profiles; target easing in the layer canvas; localised layer chips; skill picker staleness and queued Stop; chip distances from the vehicle (45bbb1c)
  • plugins: regenerate the contract registry mirror (vehicle-state body version 5) (9075a72)
  • Cockpit spec: setup strings for every flight-controller setup step, action, blocker, phase and live value; body-key fallback rule (byte copy) (2c8642b)
  • cockpit: layer stack stays still while frames stream (stable layout context, memoised stack); Settings > Controls shows saved bindings after a reload; plugin state reports refresh the skill picker; demo SIYI pod skills and Follow-Me parameters (c05173a)
  • aircraft setup: agent-run ground and air setup wizards under Settings, drawn from the setup step schema with spec text and pictures; step re-run, snapshot revert and setup report; demo setup engine (95c7178)
  • aircraft setup entry points and agent-run calibration: chip NOT READY links to setup, first-connect setup banner, calibration and autotune panels run the agent's setup step when the drone has one; cockpit minimap moves to the bottom-left card so the flight-state chip no longer covers it (c7c2e73)
  • demo setup engine: autotune runs roll and pitch then yaw with progress, live values and before/after gains; abort and retry (4eaf82b)
  • aircraft setup demo: stream frames go through the setup frame parser, as the agent's do (51c2caf)
  • demo setup engine: finishing the ground wizard streams the air wizard as available (71796e4)
  • Convex exposure guard: recognise the pairing claim bodies (claimForUser, claimForBrowser) as caller checks (fb0e99e)
  • Regenerate the route reference (aircraft setup page) and the agent capability mirror (flight.motion) (f7c0d77)
  • Typecheck: declare static asset imports from a committed reference, since next-env.d.ts is generated and gitignored (f532aa1)
  • Split source files over the size limit: plugin contribution mounts, controls cards, target marks, layer painter and engine types, pad status and stick shaping, target text helpers, demo skills, PX4 mock params; CAN forward and actuator test join the adapter's extra commands (617b45b)
  • Lockfile: Next.js 16.4.5, DOMPurify 3.4.17, zod 4.6.7, fast-uri 3.1.9 and ip-address 10.7.6 for published advisories, within the declared ranges (2f1282d)
  • Test setup: give DOM tests working Web Storage on Node 25+, whose built-in localStorage global shadows the environment's (d47ae60)
  • Cockpit: built-ins fall back to the flight controller when the pilot stalls; plan identity counts the ArduPilot home slot and claims no difference without a reported total; detection boxes dim at 500 ms and hide at 2 s with a Targets unavailable chip (aef0b52)
  • Vision model picker: only a detection model can be made the engine detector and the cockpit picker lists detection models only; the arm lock reads the picker's own drone (f254985)
  • Flight-state chip: the active mission chip shows the next waypoint's ETA from the drone's AR frame (7617ea0)
  • Mode sheet: offer the ELRS control mode when the drone is reached through a ground station, detected from the node registry (f049df6)
  • Pilot stream: client frames checked key for key against the agent's shared pilot.v1 request fixtures; frame parsers and fixtures resynced with the agent copies (link-loss action, VTOL transition) (2b4e700)
  • Extension skills: a stopped extension is named with its reason, a skill excluded for the vehicle class is refused on keys and pad too, and default keys left unbound by a clash are listed in Settings > Controls (9689e51)
  • Controller: L2/R2 drive the gimbal pitch rate through the agent, the touchpad opens a designate reticle, the cockpit asks for a button press and shows the first-connect tour, a non-standard pad reads not supported; agent-routed ground calibrations hold while armed (a94ad9e)
  • Maps: when the plan on the drone differs, the route drawn is the agent's mirror of the drone's mission, and every full map view carries the plan banner (02babcd)
  • Target and mark painting: no per-frame point objects or font keys (83069cf)
  • Cockpit: flight screen on one measured grid (a331217)
  • Shared HUD sources: byte copies of the agent's in src/lib/hud, pilot state reads surface ops, height above ground and FC warnings (39f0b37)
  • Fly Here: the pilot flies the map point when it owns the drone and takes a goto; its refusal is shown (728d7c7)
  • Status pill lists the pilot's FC warnings; the bottom row's AGL reads the pilot's height above ground (ade4048)
  • Flight screen: HUD on the video centre, honest bottom row and status pill, gimbal pad (bcdb816)
  • Pilot wire: goto frame checked against the agent's fixture; Fly Here explains the launching refusal (c2aac63)
  • Cockpit: gimbal pad leaves Space to Pause; late shell nodes go inert; portrait heading clears the top bar (a7bd1b2)
  • Record unreleased changes in the changelog (2cc694b)
  • Cockpit map card fills the card again (68962d4)
  • Fly here: the hold dialog says it takes over a running mission or skill; the pilot's control-mode refusal has a sentence; tests for the go-to route by owner and control mode (38480b1)
  • Cockpit: layer unavailable chips sit below the top bar; a stale pilot AGL shows no data instead of a fallback 0 m; Fly here explains the failsafe refusal (ef6d250)
  • Desktop Release: build the macOS installers on macos-15, since the macos-14 runner image is retired (646e44c)
  • Desktop Release: give the Next.js build a 6 GB heap, which the macOS runner's default heap is too small for (c152c68)

Full diff: v0.61.0...v0.62.0


Downloads

  • macOS: .dmg (Intel and Apple Silicon), unsigned and not notarized
  • Windows: .exe installer, unsigned
  • Linux: .AppImage

These installers are not code-signed. Check a download against
SHA256SUMS in this release (sha256sum -c SHA256SUMS --ignore-missing).

For the latest web version, visit command.altnautica.com.