0.2.0b1 (beta 1)
The first beta for invited ROS 2 teams. It replaces the 9 October 2026 test builds. See the beta page for access, known limits and feedback.
Builds
Two builds: Ubuntu 22.04 with ROS 2 Humble (Python 3.10) and Ubuntu 24.04 with ROS 2 Jazzy (Python 3.12), both x86_64. The install page lists each build's release name, archive SHA-256 and installer command. flightops --version shows the version, release and source commit of your install.
New
- Beta access. A per-device license (
flightops license activate) and required usage metrics (flightops telemetry show). See the license and metrics reference and the privacy notice. Since 21 October 2026 the installer first asks you to accept the beta terms (source repository); the builds themselves did not change. - Every tool on your PATH.
onscope,splashdown,lccandlaunchcommit,highbay,flightops-mcp,flightops-results,flightops-tui,flightops-service,flightschool,flightlead(preview) andflightops-gym-smoke(research preview) are installed withflightops. Earlier builds put onlyflightopson PATH. - Scene Workbench.
flightops workbenchopens recordings in a desktop app: replay a run as a 2D scene, or compare two runs on one cursor.--sampleopens two bundled Nav2 runs. See Scene Workbench. - Terminal views rail with Health first. Health ranks graph problems from onscope's doctor checks in every session, beside the other views. A command palette, sampled topic rates, the clock source, launch processes and recording lanes were added; Playback can seek.
- Results viewer and personal workspace page in the browser (
flightops results,flightops workspace). - Skills and coordinator.
flightschool installcopies the 14 ROS 2 skills into.claude/skills(or.agents/skillswith--agents);flightlead init DIRsets up the coordinator directory. - Offline documentation.
flightops docs --openopens the user guide shipped with the install.flightops --versionandonscope --versionwere added. - Gemini provider in the archive. The archive now includes the libraries the Gemini API provider needs, so the optional AI setup can use a Gemini API key without extra installs.
Changed
lcc initalways writeslocal_only: true; evidence leaves the machine only after you set it tofalse.lcc run --jsonprints only JSON.flightops --bag FILEenables Playback in attach mode only, and playback refuses to start on a ROS domain that has nodes Flightops did not start.- The Changes view keeps the session's first live capture as its baseline.
flightops record statusprints the scope key thatflightops retentionneeds.- The ChatGPT account route of the AI setup is labelled "preview".
- Commands print a one-line refusal instead of a Python traceback for expected errors.
- The installer refuses an unmanaged install folder, repairs a broken virtual environment, honours
--python, checks checksums strictly, and ignores your user site-packages. - The launch log keeps bursts of output and reads exit codes correctly.
Removed
- Teams publication (
flightops team), which the 9 October builds included. It is not part of the beta.
Upgrade from an earlier build
Run the beta installer from the install page. It installs the beta beside your current release and keeps the previous release. Then activate the device:
flightops license activateflightops --rollback returns to the previous release. In an earlier release, the commands that release has run without a license check, and the commands it does not have exit with code 127. Running the beta installer again restores the beta.